Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d3c532431749fbba8424d923b64b81e0b49105b0c8ef391964d821e44820cce0

Tx prefix hash: 89a3582f64ff969df90519bd705c5c041f16ab2e2df19dbb99d6823fa9e7f983
Tx public key: 3fb052d6e293a2faae31fc0a2f430998e8e3e5eda5acdc691901a1025cd6dc43
Timestamp: 1745210964 Timestamp [UCT]: 2025-04-21 04:49:24 Age [y:d:h:m:s]: 00:023:20:14:37
Block: 1266042 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 17075 RingCT/type: yes/0
Extra: 013fb052d6e293a2faae31fc0a2f430998e8e3e5eda5acdc691901a1025cd6dc4302110000000ddbb571c1000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 613eca35c9eb0208cf467cb518e76c8969bb5b490b7eaafcf457404032340112 0.600000000000 1753257 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": 1266052, "vin": [ { "gen": { "height": 1266042 } } ], "vout": [ { "amount": 600000000, "target": { "key": "613eca35c9eb0208cf467cb518e76c8969bb5b490b7eaafcf457404032340112" } } ], "extra": [ 1, 63, 176, 82, 214, 226, 147, 162, 250, 174, 49, 252, 10, 47, 67, 9, 152, 232, 227, 229, 237, 165, 172, 220, 105, 25, 1, 161, 2, 92, 214, 220, 67, 2, 17, 0, 0, 0, 13, 219, 181, 113, 193, 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