Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 3c78b0942320cdb3ec66ddb27e96de9bd0f7841daa419c2353b31827bc5581f7

Tx prefix hash: 63ff9d763aa570a222e91d3391d74a1e4776cb5d884d225bc69e25aa030be26c
Tx public key: 9817acace0f19ffca386ec1e11ea0700b7992be25e3927530a075df18b257f3d
Timestamp: 1737035386 Timestamp [UCT]: 2025-01-16 13:49:46 Age [y:d:h:m:s]: 00:156:09:30:21
Block: 1198639 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 111416 RingCT/type: yes/0
Extra: 019817acace0f19ffca386ec1e11ea0700b7992be25e3927530a075df18b257f3d021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b2886c0613fee955d5f7aae860e2c80d534793c2eb47b17e1e00cc3a92dedbe1 0.600000000000 1685264 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1198649, "vin": [ { "gen": { "height": 1198639 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b2886c0613fee955d5f7aae860e2c80d534793c2eb47b17e1e00cc3a92dedbe1" } } ], "extra": [ 1, 152, 23, 172, 172, 224, 241, 159, 252, 163, 134, 236, 30, 17, 234, 7, 0, 183, 153, 43, 226, 94, 57, 39, 83, 10, 7, 93, 241, 139, 37, 127, 61, 2, 17, 0, 0, 0, 4, 0, 127, 151, 138, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8