Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ed20719a3de2d3e27a7f240ded9be39767e2224270601c3de2c8af04bba9d091

Tx prefix hash: c23dbe888d6e36131cf4b5377814a9c7904407f51ae7220aae4eb04d7fe78e4a
Tx public key: 6e595bb93a88cbb2f90ca198a0cbb72d2949be0c53cf4392dc582ccb11a9bdb7
Timestamp: 1714901513 Timestamp [UCT]: 2024-05-05 09:31:53 Age [y:d:h:m:s]: 00:294:01:03:07
Block: 1015299 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 210143 RingCT/type: yes/0
Extra: 016e595bb93a88cbb2f90ca198a0cbb72d2949be0c53cf4392dc582ccb11a9bdb70211000000040011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1b837fc647617ee6f7bb3c8dc5f22bfad2a01fc9dca0735372fb890ed4e78cbb 0.600000000000 1478622 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": 1015309, "vin": [ { "gen": { "height": 1015299 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1b837fc647617ee6f7bb3c8dc5f22bfad2a01fc9dca0735372fb890ed4e78cbb" } } ], "extra": [ 1, 110, 89, 91, 185, 58, 136, 203, 178, 249, 12, 161, 152, 160, 203, 183, 45, 41, 73, 190, 12, 83, 207, 67, 146, 220, 88, 44, 203, 17, 169, 189, 183, 2, 17, 0, 0, 0, 4, 0, 17, 5, 91, 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