Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 77fa81db850fe729bb80de98d77674b6da2e01d753376147a1eee4a2b1743e36

Tx prefix hash: 6bff474313e100ba1bbc0849cb9acbd54fc51d103baa8926f8c547167667189c
Tx public key: cdc9d8e13b95b5fd2388d59c31c9e1b695e992d8af37a767c49e4d1a84a94451
Timestamp: 1752737316 Timestamp [UCT]: 2025-07-17 07:28:36 Age [y:d:h:m:s]: 00:170:07:15:44
Block: 1327255 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 120561 RingCT/type: yes/0
Extra: 01cdc9d8e13b95b5fd2388d59c31c9e1b695e992d8af37a767c49e4d1a84a94451021100000001a11dba98000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 868fa0b6940d9456d401ee23c96238fe4ca1b3643c1cea49b44e65775a2746c2 0.600000000000 1815008 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": 1327265, "vin": [ { "gen": { "height": 1327255 } } ], "vout": [ { "amount": 600000000, "target": { "key": "868fa0b6940d9456d401ee23c96238fe4ca1b3643c1cea49b44e65775a2746c2" } } ], "extra": [ 1, 205, 201, 216, 225, 59, 149, 181, 253, 35, 136, 213, 156, 49, 201, 225, 182, 149, 233, 146, 216, 175, 55, 167, 103, 196, 158, 77, 26, 132, 169, 68, 81, 2, 17, 0, 0, 0, 1, 161, 29, 186, 152, 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