Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0ee427d2434772d5acc6ed993b7da7a9ca77cecef13caa7f8d528b4840594dcc

Tx prefix hash: 054f92b779ee5a180e763c3a5a473718eab22747f40a5c351cbd5d794727b95f
Tx public key: 65e150a328e0c50407dfd9dce73d368dd2374abee63eb62fabb1e927b40a0076
Timestamp: 1763564300 Timestamp [UCT]: 2025-11-19 14:58:20 Age [y:d:h:m:s]: 00:050:17:30:23
Block: 1415592 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 36336 RingCT/type: yes/0
Extra: 0165e150a328e0c50407dfd9dce73d368dd2374abee63eb62fabb1e927b40a00760211000000027b1e51ac000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b22a97ea4a550615ac3e68bde1bcadb280b88a9793c4630ee40d191efee4141c 0.600000000000 1904095 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": 1415602, "vin": [ { "gen": { "height": 1415592 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b22a97ea4a550615ac3e68bde1bcadb280b88a9793c4630ee40d191efee4141c" } } ], "extra": [ 1, 101, 225, 80, 163, 40, 224, 197, 4, 7, 223, 217, 220, 231, 61, 54, 141, 210, 55, 74, 190, 230, 62, 182, 47, 171, 177, 233, 39, 180, 10, 0, 118, 2, 17, 0, 0, 0, 2, 123, 30, 81, 172, 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