Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 84f2a01b6acf7097e56dc3a741dd8de53620f6898034b54211cd19040c908cf3

Tx prefix hash: 546774778895200c1a78f3e91fff761165649535fb015c1da5fbeea9d8e49637
Tx public key: b029e57c9ec614ae4aa1ecd65dd01410de1231cc5c6babaa700c80868a6462e3
Timestamp: 1580488659 Timestamp [UCT]: 2020-01-31 16:37:39 Age [y:d:h:m:s]: 05:068:18:52:37
Block: 56091 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1200860 RingCT/type: yes/0
Extra: 01b029e57c9ec614ae4aa1ecd65dd01410de1231cc5c6babaa700c80868a6462e302110000000549b77a3d000000000000000000

1 output(s) for total of 400.081119316000 dcy

stealth address amount amount idx
00: 9b48e4e1ad9f2e34cfda205c7ae62719ca6e340becaabdb19abfbcc1118229ed 400.081119316000 103421 of 0

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": 56101, "vin": [ { "gen": { "height": 56091 } } ], "vout": [ { "amount": 400081119316, "target": { "key": "9b48e4e1ad9f2e34cfda205c7ae62719ca6e340becaabdb19abfbcc1118229ed" } } ], "extra": [ 1, 176, 41, 229, 124, 158, 198, 20, 174, 74, 161, 236, 214, 93, 208, 20, 16, 222, 18, 49, 204, 92, 107, 171, 170, 112, 12, 128, 134, 138, 100, 98, 227, 2, 17, 0, 0, 0, 5, 73, 183, 122, 61, 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