Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 85cb4a1b4ccea332c9ee9d299c0be4a720f7217c3efc32ea64fac0ff314ee5bd

Tx prefix hash: 4e5ce8811f6fa345c89a201de6a5d3514750eddc51e7b090e8773ce7d23bc9a0
Tx public key: 99046dfeadf0542670e9c990deecfa000b0f36b8a295be4e466ac7e5b53b856f
Timestamp: 1750580064 Timestamp [UCT]: 2025-06-22 08:14:24 Age [y:d:h:m:s]: 00:214:23:30:15
Block: 1310321 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 151464 RingCT/type: yes/0
Extra: 0199046dfeadf0542670e9c990deecfa000b0f36b8a295be4e466ac7e5b53b856f0211000000018368266d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 406db7dd38efe2636569d84418c6f2af9e412ab7a440e13d91a7b8d074db04e1 0.600000000000 1797940 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": 1310331, "vin": [ { "gen": { "height": 1310321 } } ], "vout": [ { "amount": 600000000, "target": { "key": "406db7dd38efe2636569d84418c6f2af9e412ab7a440e13d91a7b8d074db04e1" } } ], "extra": [ 1, 153, 4, 109, 254, 173, 240, 84, 38, 112, 233, 201, 144, 222, 236, 250, 0, 11, 15, 54, 184, 162, 149, 190, 78, 70, 106, 199, 229, 181, 59, 133, 111, 2, 17, 0, 0, 0, 1, 131, 104, 38, 109, 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