Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 301bf050015ac95eddd49e21e7d91d86710f1baa63bab47ca66d3a4e8527c838

Tx prefix hash: 6f782ade280285e92afb8257551adb5c78cbc3c38faf0f87cd2965f3c0cd4f2d
Tx public key: c21e48423fa596e2f088e881c4d1db935ed455262cb588af40c7b5d9812b7ad9
Timestamp: 1764033158 Timestamp [UCT]: 2025-11-25 01:12:38 Age [y:d:h:m:s]: 00:002:07:43:19
Block: 1419484 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 1669 RingCT/type: yes/0
Extra: 01c21e48423fa596e2f088e881c4d1db935ed455262cb588af40c7b5d9812b7ad9021100000002fb8fd089000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dd35a33efee85959a1cd1b8ecc3ab814e17164320852d218013187aa7aeb0d13 0.600000000000 1908021 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": 1419494, "vin": [ { "gen": { "height": 1419484 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dd35a33efee85959a1cd1b8ecc3ab814e17164320852d218013187aa7aeb0d13" } } ], "extra": [ 1, 194, 30, 72, 66, 63, 165, 150, 226, 240, 136, 232, 129, 196, 209, 219, 147, 94, 212, 85, 38, 44, 181, 136, 175, 64, 199, 181, 217, 129, 43, 122, 217, 2, 17, 0, 0, 0, 2, 251, 143, 208, 137, 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