Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6f42a12f720060f4699d8d6900e21e9d0b72e00075db7a29d5ef8e09f7a5ef93

Tx prefix hash: f816c3b6f35d075cad8a99b9fb2b3df0df314e50a999d28af476d11b70663437
Tx public key: 462a580df574b7e8a9b6a5e0f905fe1bbed011c940dcdf3851e07145921b7775
Timestamp: 1752631267 Timestamp [UCT]: 2025-07-16 02:01:07 Age [y:d:h:m:s]: 00:176:07:06:40
Block: 1326412 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 124824 RingCT/type: yes/0
Extra: 01462a580df574b7e8a9b6a5e0f905fe1bbed011c940dcdf3851e07145921b7775021100000001e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 111b58198558e6c07492e891223c43d6e1acb47a5bc414bffd3f76b009872896 0.600000000000 1814163 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": 1326422, "vin": [ { "gen": { "height": 1326412 } } ], "vout": [ { "amount": 600000000, "target": { "key": "111b58198558e6c07492e891223c43d6e1acb47a5bc414bffd3f76b009872896" } } ], "extra": [ 1, 70, 42, 88, 13, 245, 116, 183, 232, 169, 182, 165, 224, 249, 5, 254, 27, 190, 208, 17, 201, 64, 220, 223, 56, 81, 224, 113, 69, 146, 27, 119, 117, 2, 17, 0, 0, 0, 1, 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