Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 269d8082df9371e981104a9a3ca0874ccb922025417e0fe2382de29e35c9c44d

Tx prefix hash: 9a5fd4cbd37c66824c0f98129c49d9706685cc0825e89d1364f0b466aa5138bb
Tx public key: c19e23628e466a10e9de8bd58fdfcbe17679e902d2af75a331bcc5c9c56f2dae
Timestamp: 1751628624 Timestamp [UCT]: 2025-07-04 11:30:24 Age [y:d:h:m:s]: 00:139:14:03:12
Block: 1318556 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 98060 RingCT/type: yes/0
Extra: 01c19e23628e466a10e9de8bd58fdfcbe17679e902d2af75a331bcc5c9c56f2dae021100000002a11dba98000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3e58148a562a8cd8c18d6d23469135d30ff92c4fbf045d45c49ce12a36088ff1 0.600000000000 1806241 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": 1318566, "vin": [ { "gen": { "height": 1318556 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3e58148a562a8cd8c18d6d23469135d30ff92c4fbf045d45c49ce12a36088ff1" } } ], "extra": [ 1, 193, 158, 35, 98, 142, 70, 106, 16, 233, 222, 139, 213, 143, 223, 203, 225, 118, 121, 233, 2, 210, 175, 117, 163, 49, 188, 197, 201, 197, 111, 45, 174, 2, 17, 0, 0, 0, 2, 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