Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f116a9e7ab0b494a31d30ba8f0de964a1e0556952fb2f2952afc72c4553876f6

Tx prefix hash: d933bb8d584a4acb181a380648bc94dbd337f7c09095010ad8f1072e8af7dd0f
Tx public key: 9d178d381c83af1dd33414e9fe5cc7dc5f3bc290d9252bf3d458f8334c472b3c
Timestamp: 1759714737 Timestamp [UCT]: 2025-10-06 01:38:57 Age [y:d:h:m:s]: 00:117:17:12:20
Block: 1383686 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 84110 RingCT/type: yes/0
Extra: 019d178d381c83af1dd33414e9fe5cc7dc5f3bc290d9252bf3d458f8334c472b3c02110000000797baf922000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 625571ba9722e6e599dd0494ff3f6e6caf097a5cddc0339bc7200ad0d881b43b 0.600000000000 1871833 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": 1383696, "vin": [ { "gen": { "height": 1383686 } } ], "vout": [ { "amount": 600000000, "target": { "key": "625571ba9722e6e599dd0494ff3f6e6caf097a5cddc0339bc7200ad0d881b43b" } } ], "extra": [ 1, 157, 23, 141, 56, 28, 131, 175, 29, 211, 52, 20, 233, 254, 92, 199, 220, 95, 59, 194, 144, 217, 37, 43, 243, 212, 88, 248, 51, 76, 71, 43, 60, 2, 17, 0, 0, 0, 7, 151, 186, 249, 34, 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