Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bed38d75c87e42fa18743e685d13296cfc3698e43e6a018bcd391b5dc1da020b

Tx prefix hash: 803ea772fcc690280c5848acd554895a8e3305987af381e959053043d3021c51
Tx public key: a90d69e656461180f9f6b714fe38c5b1adeb5c5f0d5fba8c803c09ffec9cc8b8
Timestamp: 1761288318 Timestamp [UCT]: 2025-10-24 06:45:18 Age [y:d:h:m:s]: 00:021:03:31:01
Block: 1396752 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 15128 RingCT/type: yes/0
Extra: 01a90d69e656461180f9f6b714fe38c5b1adeb5c5f0d5fba8c803c09ffec9cc8b8021100000002df5a247a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 849960e9c0ca708f9099647d1e330ac6bb57d2717dc5ec54be87b844d9d1a5f2 0.600000000000 1885039 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": 1396762, "vin": [ { "gen": { "height": 1396752 } } ], "vout": [ { "amount": 600000000, "target": { "key": "849960e9c0ca708f9099647d1e330ac6bb57d2717dc5ec54be87b844d9d1a5f2" } } ], "extra": [ 1, 169, 13, 105, 230, 86, 70, 17, 128, 249, 246, 183, 20, 254, 56, 197, 177, 173, 235, 92, 95, 13, 95, 186, 140, 128, 60, 9, 255, 236, 156, 200, 184, 2, 17, 0, 0, 0, 2, 223, 90, 36, 122, 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