Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0a3ff8e1b369e565af1f0cabdd4f3da51c78d6774414297ee475ed698eb073cc

Tx prefix hash: 007c9dc3229b33ed3e8e3eaac1f489ec709c0c9e52a200da190240c0ee618595
Tx public key: e69b9423d89b5d7b5cf222257411aef0ef6483226007fb576b0618f776e02a5b
Timestamp: 1765015353 Timestamp [UCT]: 2025-12-06 10:02:33 Age [y:d:h:m:s]: 00:017:12:46:59
Block: 1427620 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 12544 RingCT/type: yes/0
Extra: 01e69b9423d89b5d7b5cf222257411aef0ef6483226007fb576b0618f776e02a5b021100000003d6e19d7c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ae921f8b082b84f758b8640d4a2030f9ad00b1e82d1fb9033228821afba71d21 0.600000000000 1916323 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": 1427630, "vin": [ { "gen": { "height": 1427620 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ae921f8b082b84f758b8640d4a2030f9ad00b1e82d1fb9033228821afba71d21" } } ], "extra": [ 1, 230, 155, 148, 35, 216, 155, 93, 123, 92, 242, 34, 37, 116, 17, 174, 240, 239, 100, 131, 34, 96, 7, 251, 87, 107, 6, 24, 247, 118, 224, 42, 91, 2, 17, 0, 0, 0, 3, 214, 225, 157, 124, 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