Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: db19c5a9bbff4d3592d2ab21c076a2ee500aebfadd668ab69691553c4fa93423

Tx prefix hash: ec81304804287887229069f19f6c4f6fb86043e353a52b61478f5e6f9aa1c663
Tx public key: a8bd936d30c35366d7e78ced3d370b22aa7a88094f6b3ca410a48f1f04909588
Timestamp: 1738011453 Timestamp [UCT]: 2025-01-27 20:57:33 Age [y:d:h:m:s]: 00:045:19:01:27
Block: 1206479 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 32751 RingCT/type: yes/0
Extra: 01a8bd936d30c35366d7e78ced3d370b22aa7a88094f6b3ca410a48f1f0490958802110000000a1f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5324f0df6f842c3290541c3798415442c085dcc424af00f50b4ef3209515b7e0 0.600000000000 1693188 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": 1206489, "vin": [ { "gen": { "height": 1206479 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5324f0df6f842c3290541c3798415442c085dcc424af00f50b4ef3209515b7e0" } } ], "extra": [ 1, 168, 189, 147, 109, 48, 195, 83, 102, 215, 231, 140, 237, 61, 55, 11, 34, 170, 122, 136, 9, 79, 107, 60, 164, 16, 164, 143, 31, 4, 144, 149, 136, 2, 17, 0, 0, 0, 10, 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