Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dc9b02360391d24112051c202f553bd947ce2b85c63b8d66df36a25a67c561f4

Tx prefix hash: e0a213b6902034d48ee102e5623b955df69b2b516984a0ad23629dc5803e4ec2
Tx public key: f7fc3c6e26e9c417598bab1aaca12a58503d45cd60d5673684fb6a291ba59cef
Timestamp: 1752031744 Timestamp [UCT]: 2025-07-09 03:29:04 Age [y:d:h:m:s]: 00:208:01:02:35
Block: 1321698 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 147105 RingCT/type: yes/0
Extra: 01f7fc3c6e26e9c417598bab1aaca12a58503d45cd60d5673684fb6a291ba59cef021100000002e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0b0c7f8a1e60ced2e00dfa32919a3171d3d2199730077eed71c624e60c88d07a 0.600000000000 1809405 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": 1321708, "vin": [ { "gen": { "height": 1321698 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0b0c7f8a1e60ced2e00dfa32919a3171d3d2199730077eed71c624e60c88d07a" } } ], "extra": [ 1, 247, 252, 60, 110, 38, 233, 196, 23, 89, 139, 171, 26, 172, 161, 42, 88, 80, 61, 69, 205, 96, 213, 103, 54, 132, 251, 106, 41, 27, 165, 156, 239, 2, 17, 0, 0, 0, 2, 228, 220, 144, 9, 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