Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6413dcbaef8be31f658926cb1d290be2eb765b2ef80222f77fb277dcca1445b0

Tx prefix hash: a733ca94227ca5650e3cf80fe4101a0be4b4e10f4684af000821408006338a6f
Tx public key: ea62962223a0f588feba92c8e655c42bc94ef612606d724d1f7cc6a84a2b8ec8
Timestamp: 1648503132 Timestamp [UCT]: 2022-03-28 21:32:12 Age [y:d:h:m:s]: 02:316:13:31:32
Block: 468477 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 745560 RingCT/type: yes/0
Extra: 01ea62962223a0f588feba92c8e655c42bc94ef612606d724d1f7cc6a84a2b8ec802110000001206faf294000000000000000000

1 output(s) for total of 17.208438998000 dcy

stealth address amount amount idx
00: c1a333d713d9f7d8a22bc0ce440aaad2d7cc7b9416dc8ca56fc12d330e80b0e9 17.208438998000 887205 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": 468487, "vin": [ { "gen": { "height": 468477 } } ], "vout": [ { "amount": 17208438998, "target": { "key": "c1a333d713d9f7d8a22bc0ce440aaad2d7cc7b9416dc8ca56fc12d330e80b0e9" } } ], "extra": [ 1, 234, 98, 150, 34, 35, 160, 245, 136, 254, 186, 146, 200, 230, 85, 196, 43, 201, 78, 246, 18, 96, 109, 114, 77, 31, 124, 198, 168, 74, 43, 142, 200, 2, 17, 0, 0, 0, 18, 6, 250, 242, 148, 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