Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9ec75e1412d3da1314a1b0c0df412b2631e6d64fca58767af111901a69ff8a50

Tx prefix hash: 9a4fbf0c29656e7c37607cbeff7006df1135b0f7b2c69a783f3a5e23270c7551
Tx public key: b607a10aab743bf7d9094f7447181641eb817f0aedb5b5f01fd3275754cee0bf
Timestamp: 1711973192 Timestamp [UCT]: 2024-04-01 12:06:32 Age [y:d:h:m:s]: 01:247:08:02:37
Block: 990980 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 435531 RingCT/type: yes/0
Extra: 01b607a10aab743bf7d9094f7447181641eb817f0aedb5b5f01fd3275754cee0bf0211000000057a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 005e79bcf00119db85b5e2fc5037324d9099570127a68dff6e9c3c86f51e7d84 0.600000000000 1451312 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": 990990, "vin": [ { "gen": { "height": 990980 } } ], "vout": [ { "amount": 600000000, "target": { "key": "005e79bcf00119db85b5e2fc5037324d9099570127a68dff6e9c3c86f51e7d84" } } ], "extra": [ 1, 182, 7, 161, 10, 171, 116, 59, 247, 217, 9, 79, 116, 71, 24, 22, 65, 235, 129, 127, 10, 237, 181, 181, 240, 31, 211, 39, 87, 84, 206, 224, 191, 2, 17, 0, 0, 0, 5, 122, 156, 244, 199, 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