Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3be33c29fc8c31df02ae000c02e9f2df567903ed6241488232e85ad2d0b9aecd

Tx prefix hash: ee9b2f7310f77791c9c211da8cd1163759cc6283ed7bd965a612fe8eb9a6f8c6
Tx public key: 1dd0b6498c3c1c353a972a370a92a7afca5f894ba72ea265c5d49cbcb98d8e54
Timestamp: 1760177548 Timestamp [UCT]: 2025-10-11 10:12:28 Age [y:d:h:m:s]: 00:088:00:15:27
Block: 1387531 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 63020 RingCT/type: yes/0
Extra: 011dd0b6498c3c1c353a972a370a92a7afca5f894ba72ea265c5d49cbcb98d8e54021100000001d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 458b9c23dfe6de86efd69a0ab7def96ed15c5ccd0357a83b4fb79664249ca4b9 0.600000000000 1875726 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": 1387541, "vin": [ { "gen": { "height": 1387531 } } ], "vout": [ { "amount": 600000000, "target": { "key": "458b9c23dfe6de86efd69a0ab7def96ed15c5ccd0357a83b4fb79664249ca4b9" } } ], "extra": [ 1, 29, 208, 182, 73, 140, 60, 28, 53, 58, 151, 42, 55, 10, 146, 167, 175, 202, 95, 137, 75, 167, 46, 162, 101, 197, 212, 156, 188, 185, 141, 142, 84, 2, 17, 0, 0, 0, 1, 216, 231, 210, 65, 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