Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 932f7c9c10b99a9930d6b8eaf512fd504d9a4213533bf831fe89a55ed01b807f

Tx prefix hash: 4a75d79c30f8275613665f80a8efd6faf44dc06b503b24c321f41bde99849026
Tx public key: 4711a0ca9baf252f6be3ef1451191a8f223bf8eab13320835a1f3d9bf89cac3f
Timestamp: 1761697252 Timestamp [UCT]: 2025-10-29 00:20:52 Age [y:d:h:m:s]: 00:011:07:16:58
Block: 1400136 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 8082 RingCT/type: yes/0
Extra: 014711a0ca9baf252f6be3ef1451191a8f223bf8eab13320835a1f3d9bf89cac3f02110000000125a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 83bf7352c89c8e70c91666c16111beca9ab55038e64751c3c5f21b8eb16c0345 0.600000000000 1888443 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": 1400146, "vin": [ { "gen": { "height": 1400136 } } ], "vout": [ { "amount": 600000000, "target": { "key": "83bf7352c89c8e70c91666c16111beca9ab55038e64751c3c5f21b8eb16c0345" } } ], "extra": [ 1, 71, 17, 160, 202, 155, 175, 37, 47, 107, 227, 239, 20, 81, 25, 26, 143, 34, 59, 248, 234, 177, 51, 32, 131, 90, 31, 61, 155, 248, 156, 172, 63, 2, 17, 0, 0, 0, 1, 37, 163, 90, 15, 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