Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1eeeb4d68bb7cd8b36dc9f8c6973ec34b4042457ae2172f44a6953425831eaf7

Tx prefix hash: 8361ccb4d4eb67f3a4df76686aea5eb052d200eaf850f1e2ba414b814f54c13f
Tx public key: 18aadcf9fbbe0a55aed437491830e9ffff782fddfac93c3d3c7416cf3719f18d
Timestamp: 1704940817 Timestamp [UCT]: 2024-01-11 02:40:17 Age [y:d:h:m:s]: 01:078:09:33:16
Block: 932691 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 317136 RingCT/type: yes/0
Extra: 0118aadcf9fbbe0a55aed437491830e9ffff782fddfac93c3d3c7416cf3719f18d0211000000019da8e134000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8fb14f95dc196f25316889d3a6cfa1b38d26fa190e9c54300beb315c3c5312b2 0.600000000000 1390629 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": 932701, "vin": [ { "gen": { "height": 932691 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8fb14f95dc196f25316889d3a6cfa1b38d26fa190e9c54300beb315c3c5312b2" } } ], "extra": [ 1, 24, 170, 220, 249, 251, 190, 10, 85, 174, 212, 55, 73, 24, 48, 233, 255, 255, 120, 47, 221, 250, 201, 60, 61, 60, 116, 22, 207, 55, 25, 241, 141, 2, 17, 0, 0, 0, 1, 157, 168, 225, 52, 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