Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3adb22f9c5bd08f2163e12ff1bec829ac07ef638290b01b70d133212a397b5fc

Tx prefix hash: 1f0e9c7202691aac10e73bec000923ae1881192fe9ffd1fc6c82f423430fd450
Tx public key: af5a57084c0689fdf6bba5c4e7190d4ace5b54795f99ab4f92eacfb0ce2f3e75
Timestamp: 1705336103 Timestamp [UCT]: 2024-01-15 16:28:23 Age [y:d:h:m:s]: 01:295:09:54:38
Block: 935970 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 469929 RingCT/type: yes/0
Extra: 01af5a57084c0689fdf6bba5c4e7190d4ace5b54795f99ab4f92eacfb0ce2f3e750211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 406f5ba4098a6074736888376612f8623654706a95c598debd350d331aa6a8bc 0.600000000000 1393992 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": 935980, "vin": [ { "gen": { "height": 935970 } } ], "vout": [ { "amount": 600000000, "target": { "key": "406f5ba4098a6074736888376612f8623654706a95c598debd350d331aa6a8bc" } } ], "extra": [ 1, 175, 90, 87, 8, 76, 6, 137, 253, 246, 187, 165, 196, 231, 25, 13, 74, 206, 91, 84, 121, 95, 153, 171, 79, 146, 234, 207, 176, 206, 47, 62, 117, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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