Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dd3f979f76b53636d96aa71d4032401f91daca3b523b8fe9bb52f44043b9da8f

Tx prefix hash: df8499da5bf4b75c3085adf338b326e89ed0ceda2a57b855a0601860e9e0f071
Tx public key: 5908f18191ed5a3a51e5e79815a4885f86b5958d58887d2ecead2a5ffb8be3da
Timestamp: 1761266168 Timestamp [UCT]: 2025-10-24 00:36:08 Age [y:d:h:m:s]: 00:016:03:16:59
Block: 1396567 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 11540 RingCT/type: yes/0
Extra: 015908f18191ed5a3a51e5e79815a4885f86b5958d58887d2ecead2a5ffb8be3da021100000001e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9b701bde0d4820a0fbd68f0466257f9c06b4df13a22d12aa7406c9ede2141a7c 0.600000000000 1884854 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": 1396577, "vin": [ { "gen": { "height": 1396567 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9b701bde0d4820a0fbd68f0466257f9c06b4df13a22d12aa7406c9ede2141a7c" } } ], "extra": [ 1, 89, 8, 241, 129, 145, 237, 90, 58, 81, 229, 231, 152, 21, 164, 136, 95, 134, 181, 149, 141, 88, 136, 125, 46, 206, 173, 42, 95, 251, 139, 227, 218, 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