Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a11ba109abd3a81c294bcc9bfa41ad333daa1e4af21c391f88a8cd7aa0efe99e

Tx prefix hash: f669fd902ab21169077c4d1a6abf3fe28f06fdd7f7d97e5d05e038f0ac242018
Tx public key: 40384a77857c800fb5b4a53ece0a773fb2c160e5d66bf23975ff490b5d65b0a2
Timestamp: 1759429514 Timestamp [UCT]: 2025-10-02 18:25:14 Age [y:d:h:m:s]: 00:119:09:23:27
Block: 1381327 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 85312 RingCT/type: yes/0
Extra: 0140384a77857c800fb5b4a53ece0a773fb2c160e5d66bf23975ff490b5d65b0a202110000001b97baf922000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 22c1b440ada9b511582171be54f0b03cbeffdb02bb81207607be6c48d77519b0 0.600000000000 1869446 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": 1381337, "vin": [ { "gen": { "height": 1381327 } } ], "vout": [ { "amount": 600000000, "target": { "key": "22c1b440ada9b511582171be54f0b03cbeffdb02bb81207607be6c48d77519b0" } } ], "extra": [ 1, 64, 56, 74, 119, 133, 124, 128, 15, 181, 180, 165, 62, 206, 10, 119, 63, 178, 193, 96, 229, 214, 107, 242, 57, 117, 255, 73, 11, 93, 101, 176, 162, 2, 17, 0, 0, 0, 27, 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