Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 57b56a8516877168640924567cb5973c244f180c2bd759467e7e0afe70821f8c

Tx prefix hash: e6742bf4476c5f49cfb7823339a1a4b859c236d3c4668313a55d42cf8da55a12
Tx public key: 786e39e53cd1587ee4a73a4acf27935efa34ef3d838e386c6370bbef92839d83
Timestamp: 1581821177 Timestamp [UCT]: 2020-02-16 02:46:17 Age [y:d:h:m:s]: 04:317:11:37:01
Block: 65745 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1119314 RingCT/type: yes/0
Extra: 01786e39e53cd1587ee4a73a4acf27935efa34ef3d838e386c6370bbef92839d830211000000040aca7173000000000000000000

1 output(s) for total of 371.695207820000 dcy

stealth address amount amount idx
00: 73c1f82d9e97823110aae47a2d5bcd11e6bda285e9d182877f00a3d883f256a8 371.695207820000 121322 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": 65755, "vin": [ { "gen": { "height": 65745 } } ], "vout": [ { "amount": 371695207820, "target": { "key": "73c1f82d9e97823110aae47a2d5bcd11e6bda285e9d182877f00a3d883f256a8" } } ], "extra": [ 1, 120, 110, 57, 229, 60, 209, 88, 126, 228, 167, 58, 74, 207, 39, 147, 94, 250, 52, 239, 61, 131, 142, 56, 108, 99, 112, 187, 239, 146, 131, 157, 131, 2, 17, 0, 0, 0, 4, 10, 202, 113, 115, 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