Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4adaf439e9e8c3a9b35a03e7ba6880d333a73b2b52d09a01347788ec0b961c68

Tx prefix hash: 0c6f4069e13b7c196871150fc0239208d9b274a4d02a6d3b844bea6116e4083c
Tx public key: 7d0382ff3cab4622034db1d4d4d140edefd02ff9e1a2e14c4725ef4099c92c82
Timestamp: 1763047495 Timestamp [UCT]: 2025-11-13 15:24:55 Age [y:d:h:m:s]: 00:056:03:04:17
Block: 1411311 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 40198 RingCT/type: yes/0
Extra: 017d0382ff3cab4622034db1d4d4d140edefd02ff9e1a2e14c4725ef4099c92c820211000000012609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: abbffcd099cd1c28ba823c9ccbfe3593a2829fc39b0092cc63a190b2f8a6c890 0.600000000000 1899772 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": 1411321, "vin": [ { "gen": { "height": 1411311 } } ], "vout": [ { "amount": 600000000, "target": { "key": "abbffcd099cd1c28ba823c9ccbfe3593a2829fc39b0092cc63a190b2f8a6c890" } } ], "extra": [ 1, 125, 3, 130, 255, 60, 171, 70, 34, 3, 77, 177, 212, 212, 209, 64, 237, 239, 208, 47, 249, 225, 162, 225, 76, 71, 37, 239, 64, 153, 201, 44, 130, 2, 17, 0, 0, 0, 1, 38, 9, 179, 160, 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