Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 863f53e1aff31c8ec19ad000746eb2097c1bca18e7c4d3bde8b78e28b6a52339

Tx prefix hash: 12f808f862f4f75e9a8f28f131b8d7dc9019476842e8191c5b896b2cebe85736
Tx public key: b55b56e724df13122f08a13d73867378d1d92464be84647ea7172cd9d03c4f93
Timestamp: 1710522112 Timestamp [UCT]: 2024-03-15 17:01:52 Age [y:d:h:m:s]: 01:061:04:51:14
Block: 978997 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 304733 RingCT/type: yes/0
Extra: 01b55b56e724df13122f08a13d73867378d1d92464be84647ea7172cd9d03c4f9302110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 61cb55a5372628df3b327389e80d2091312e028d931bb20d404b766bef146b91 0.600000000000 1439026 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": 979007, "vin": [ { "gen": { "height": 978997 } } ], "vout": [ { "amount": 600000000, "target": { "key": "61cb55a5372628df3b327389e80d2091312e028d931bb20d404b766bef146b91" } } ], "extra": [ 1, 181, 91, 86, 231, 36, 223, 19, 18, 47, 8, 161, 61, 115, 134, 115, 120, 209, 217, 36, 100, 190, 132, 100, 126, 167, 23, 44, 217, 208, 60, 79, 147, 2, 17, 0, 0, 0, 2, 82, 212, 126, 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