Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6818a13b730df530a7793441644034842390aeff8b41b926995f160bea97f110

Tx prefix hash: 5fc2e7d1dde4e3cb38e1a8d46dabb9954ea9426aa1742a4234908d3420d220af
Tx public key: 5c2a9e35dd6a6d888d683e24ecc9dbf4fdfde7db0411995c9c029dd14ad9ab85
Timestamp: 1735258734 Timestamp [UCT]: 2024-12-27 00:18:54 Age [y:d:h:m:s]: 00:324:04:58:53
Block: 1183932 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 229224 RingCT/type: yes/0
Extra: 015c2a9e35dd6a6d888d683e24ecc9dbf4fdfde7db0411995c9c029dd14ad9ab850211000000061f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1e28da4523227326cbad86b48177f593ee4b38df9187010893c2e54e4e6d68c8 0.600000000000 1670381 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": 1183942, "vin": [ { "gen": { "height": 1183932 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1e28da4523227326cbad86b48177f593ee4b38df9187010893c2e54e4e6d68c8" } } ], "extra": [ 1, 92, 42, 158, 53, 221, 106, 109, 136, 141, 104, 62, 36, 236, 201, 219, 244, 253, 253, 231, 219, 4, 17, 153, 92, 156, 2, 157, 209, 74, 217, 171, 133, 2, 17, 0, 0, 0, 6, 31, 10, 83, 235, 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