Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7d42d7a0e10641d07296649ae3e092d7fdae798876f31856669ac640b996dbd9

Tx prefix hash: d4bf3042b30ed936674ea3a9f73e02df1b994977c65892d6d7f7f954d92bc1e1
Tx public key: a5e9e9439adc9a51e639f2dc70c9fa6d773b1cee5daa7f57ec8efed94cfa909f
Timestamp: 1765890597 Timestamp [UCT]: 2025-12-16 13:09:57 Age [y:d:h:m:s]: 00:046:20:41:38
Block: 1434874 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 33374 RingCT/type: yes/0
Extra: 01a5e9e9439adc9a51e639f2dc70c9fa6d773b1cee5daa7f57ec8efed94cfa909f0211000000037b1e51ac000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0d4bf3908af0e2e26ca8f4f88b07fd595eda9c1e06c7d6e54f2a99cccda58032 0.600000000000 1923671 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": 1434884, "vin": [ { "gen": { "height": 1434874 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0d4bf3908af0e2e26ca8f4f88b07fd595eda9c1e06c7d6e54f2a99cccda58032" } } ], "extra": [ 1, 165, 233, 233, 67, 154, 220, 154, 81, 230, 57, 242, 220, 112, 201, 250, 109, 119, 59, 28, 238, 93, 170, 127, 87, 236, 142, 254, 217, 76, 250, 144, 159, 2, 17, 0, 0, 0, 3, 123, 30, 81, 172, 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