Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 18e0a058b4ed87ef1b255227d81266b8b4cc736f12f71b8e98d8bdbdcaed6b12

Tx prefix hash: fbe63a5b62878923d8e02da332b931546d6df79acc82c17adaa217f2e410191e
Tx public key: da978024af736da2021a8ff3c0c4ef3747511b1a2f20e1a8ca758e905bfe0049
Timestamp: 1751060341 Timestamp [UCT]: 2025-06-27 21:39:01 Age [y:d:h:m:s]: 00:146:03:52:26
Block: 1314096 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 102520 RingCT/type: yes/0
Extra: 01da978024af736da2021a8ff3c0c4ef3747511b1a2f20e1a8ca758e905bfe0049021100000001d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f9580e4a779e82bef014d20a79486d68871154b321ea1e41e6e5529afc1e5705 0.600000000000 1801741 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": 1314106, "vin": [ { "gen": { "height": 1314096 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f9580e4a779e82bef014d20a79486d68871154b321ea1e41e6e5529afc1e5705" } } ], "extra": [ 1, 218, 151, 128, 36, 175, 115, 109, 162, 2, 26, 143, 243, 192, 196, 239, 55, 71, 81, 27, 26, 47, 32, 225, 168, 202, 117, 142, 144, 91, 254, 0, 73, 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