Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0b43a6cd8b4f9d6386945d21a7da1eb2fb74c72b271d5d056b497ce0347aafa2

Tx prefix hash: 9f4eea1b5ca455e3406b2441f98ab06b9c45c54cac563dfc000a3872cf1e8966
Tx public key: 7469823a40767cd71fbffca7f2479fe9f727e13793dd2d660bffbcd7fbf423d2
Timestamp: 1761480817 Timestamp [UCT]: 2025-10-26 12:13:37 Age [y:d:h:m:s]: 00:058:15:26:25
Block: 1398340 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 41970 RingCT/type: yes/0
Extra: 017469823a40767cd71fbffca7f2479fe9f727e13793dd2d660bffbcd7fbf423d20211000000015dfbbe2a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5c160c3f74ab90e30891386b35728f9a8a4f902cb2adae4bd8d952a80078f514 0.600000000000 1886637 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": 1398350, "vin": [ { "gen": { "height": 1398340 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5c160c3f74ab90e30891386b35728f9a8a4f902cb2adae4bd8d952a80078f514" } } ], "extra": [ 1, 116, 105, 130, 58, 64, 118, 124, 215, 31, 191, 252, 167, 242, 71, 159, 233, 247, 39, 225, 55, 147, 221, 45, 102, 11, 255, 188, 215, 251, 244, 35, 210, 2, 17, 0, 0, 0, 1, 93, 251, 190, 42, 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