Output
sf.substreams.sink.entity.v1.EntityChanges
Inputs

Package ref
antelope-transactions@v0.5.0Run package
CLI
Run graph_out from the command line.
substreams run antelope-transactions@v0.5.0 graph_out --start-block -1substreams auth or directly on thegraph.market (see docs).README
Antelope TransactionsTransactions, Decoded Actions & Database Operations
WAX, EOS, Ultra, Telos...
sf.antelope.type.v1.Block
4bAe7NA8b6J14ZfZr3TXfzzjjSoGECTFuqv7CwnK1zzg2RNdhL5p62dGN5UqKtsSEhYZiTJbFcuuhzk9qRJj8QeU241204803332115691899435919927592795969875524131862983855247417910116163418459544660660697512970420034067948120535763746642726326018982449681191462590993{base_url}/api/{api-key}/subgraphs/id/{subgraph_id}| Chain | Subgraph ID |
|---|---|
| WAX | 4bAe7NA8b6J14ZfZr3TXfzzjjSoGECTFuqv7CwnK1zzg |
| EOS | 2RNdhL5p62dGN5UqKtsSEhYZiTJbFcuuhzk9qRJj8QeU |
| Chain | Subgraph ID (UInt256) |
|---|---|
| WAX | 24120480333211569189943591992759279596987552413186298385524741791011616341845 |
| EOS | 9544660660697512970420034067948120535763746642726326018982449681191462590993 |
{
actions(
where: {isNotify: false, account: "eosio.token"}
orderBy: block_number
orderDirection: desc
) {
timestamp
block_number
transaction {
id
}
account
name
jsonData
dbOps {
code
tableName
primaryKey
newDataJson
}
}
}
graph TD;
graph_out[map: graph_out];
sf.antelope.type.v1.Block[source: sf.antelope.type.v1.Block] --> graph_out;
code:mycontractcode:tethertether && action:issuecode:eosio.token && action:transfer && (data.to:myaccount || data.from:myaccount)auth:myaccount@activecode:atomicassets && action:logmintThese are the expressions that can be used in queries:
action:<action_name> - action namecode:<account> - smart contract account namereceiver:<account> - action receiver accountauth: - account which authority was used to sign the action, i.e.
auth:<account> - account with any permissionauth:<account>@<permission> - account with a specific permissioninput:true - will match only the top-level actionsnotif:true - will match only notifications, excluding input action or other inline actions.data.<field>: - will decode and match action parameters (doesn't support nested objects). Some examples:
data.from:myaccountdata.memo:"your daily staking rewards"db.table:<table_name>db.table:<table_name>/<scope>Queries can include && and || logical operands, as well as ( and ) parenthesis.
Modules
Output
sf.substreams.sink.entity.v1.EntityChanges
Inputs
Output
sf.substreams.index.v1.Keys