Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8a2647b1ad1bf49d2ac6e28b36126f552dff76dc14d9df5f86e63b54b8f3067e

Tx prefix hash: c67c907d7c9eab61fe53840fdd1ef94df22ec29d5c0f0f228d535bcbb12173c9
Tx public key: ace83f356c290112357b2bbb8356ce95eac4d04becd63203fd8b1bcf5c0a3992
Timestamp: 1711317279 Timestamp [UCT]: 2024-03-24 21:54:39 Age [y:d:h:m:s]: 01:285:03:55:08
Block: 985591 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 462556 RingCT/type: yes/0
Extra: 01ace83f356c290112357b2bbb8356ce95eac4d04becd63203fd8b1bcf5c0a39920211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 86e56b6b14e2ef60e327bde7a062dba41f34560978ea20a77151f98582e2d049 0.600000000000 1445808 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": 985601, "vin": [ { "gen": { "height": 985591 } } ], "vout": [ { "amount": 600000000, "target": { "key": "86e56b6b14e2ef60e327bde7a062dba41f34560978ea20a77151f98582e2d049" } } ], "extra": [ 1, 172, 232, 63, 53, 108, 41, 1, 18, 53, 123, 43, 187, 131, 86, 206, 149, 234, 196, 208, 75, 236, 214, 50, 3, 253, 139, 27, 207, 92, 10, 57, 146, 2, 17, 0, 0, 0, 4, 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