Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1233fbffa5da7b5c9a7bdc97eaee47fafec95fdad4b36f40df4c6678b348071b

Tx prefix hash: 4f547a7634e64526294d5dfc0f68a07741a8125efe89bce80aa5daab0e706b01
Tx public key: b68b916294dfa2a0cff2f1aebf87b1b58b23771e271abb5647794c12f8c25cd0
Timestamp: 1761932814 Timestamp [UCT]: 2025-10-31 17:46:54 Age [y:d:h:m:s]: 00:006:04:29:45
Block: 1402089 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 4416 RingCT/type: yes/0
Extra: 01b68b916294dfa2a0cff2f1aebf87b1b58b23771e271abb5647794c12f8c25cd00211000000022609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7e6e3397d87431e8e14f7dbda25680483a4eb39d29eaf10bb0a2df754e886064 0.600000000000 1890408 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": 1402099, "vin": [ { "gen": { "height": 1402089 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7e6e3397d87431e8e14f7dbda25680483a4eb39d29eaf10bb0a2df754e886064" } } ], "extra": [ 1, 182, 139, 145, 98, 148, 223, 162, 160, 207, 242, 241, 174, 191, 135, 177, 181, 139, 35, 119, 30, 39, 26, 187, 86, 71, 121, 76, 18, 248, 194, 92, 208, 2, 17, 0, 0, 0, 2, 38, 9, 179, 160, 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