Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 97719dff3f0d157eec07cb8718bd6b9e6b40025f07c67ccf4c633f881028e4e4

Tx prefix hash: 369b0cd91291eab08b6f820b0dc3421fb7b7e4cf254f3ff6ab7d0aecd368b2b5
Tx public key: d4bdca048ab51ae6bc524aada4163c25bb521c821dab38e1db08823f87f8a4e2
Timestamp: 1678809882 Timestamp [UCT]: 2023-03-14 16:04:42 Age [y:d:h:m:s]: 02:209:14:08:22
Block: 716967 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 669011 RingCT/type: yes/0
Extra: 01d4bdca048ab51ae6bc524aada4163c25bb521c821dab38e1db08823f87f8a4e20211000000045029cbac000000000000000000

1 output(s) for total of 2.584583636000 dcy

stealth address amount amount idx
00: 7ce7d0eec933473becccd27b3da6df5c7b68cc327414a031b0409ef1ebc42d92 2.584583636000 1161458 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": 716977, "vin": [ { "gen": { "height": 716967 } } ], "vout": [ { "amount": 2584583636, "target": { "key": "7ce7d0eec933473becccd27b3da6df5c7b68cc327414a031b0409ef1ebc42d92" } } ], "extra": [ 1, 212, 189, 202, 4, 138, 181, 26, 230, 188, 82, 74, 173, 164, 22, 60, 37, 187, 82, 28, 130, 29, 171, 56, 225, 219, 8, 130, 63, 135, 248, 164, 226, 2, 17, 0, 0, 0, 4, 80, 41, 203, 172, 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