Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2a5cfe0bc564d9e5f5b9ca1e060b4ed66c8b84b190b7309358a2b4a1d75b8491

Tx prefix hash: 58706d83974ff8b97a71fcc2f5e998aca7546d9b1de62336e711431a96803f6c
Tx public key: 4d680e7dc137b641ba1201646e2fe57aaac2097a77b6b881c0aab9f2d42a5430
Timestamp: 1763559738 Timestamp [UCT]: 2025-11-19 13:42:18 Age [y:d:h:m:s]: 00:045:00:41:44
Block: 1415553 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 32261 RingCT/type: yes/0
Extra: 014d680e7dc137b641ba1201646e2fe57aaac2097a77b6b881c0aab9f2d42a5430021100000001defb8f18000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7f240fc604aa2db313308bccf31e2d1f724984a7ceca5453ce17f01792950119 0.600000000000 1904056 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": 1415563, "vin": [ { "gen": { "height": 1415553 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7f240fc604aa2db313308bccf31e2d1f724984a7ceca5453ce17f01792950119" } } ], "extra": [ 1, 77, 104, 14, 125, 193, 55, 182, 65, 186, 18, 1, 100, 110, 47, 229, 122, 170, 194, 9, 122, 119, 182, 184, 129, 192, 170, 185, 242, 212, 42, 84, 48, 2, 17, 0, 0, 0, 1, 222, 251, 143, 24, 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