Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d180fde8a12b8ebb59ae229e7dfbd5e7a4887b051218f72a4dc04f8ec627d233

Tx prefix hash: 43439c6d002f140833040095ce60260750aa50026cfc3aab7150a73a7dbd2672
Tx public key: b672bc5565965cb63ce3d34f721b25e6c2138af50b737d4f9bd8d9fb1a5ac976
Timestamp: 1743962709 Timestamp [UCT]: 2025-04-06 18:05:09 Age [y:d:h:m:s]: 00:278:22:07:12
Block: 1255711 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 197164 RingCT/type: yes/0
Extra: 01b672bc5565965cb63ce3d34f721b25e6c2138af50b737d4f9bd8d9fb1a5ac97602110000000d6c98aa3d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c7e3b7c8a6772c18987bf308ded653caf1bae61db59199a5f00e8885e719be9d 0.600000000000 1742816 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": 1255721, "vin": [ { "gen": { "height": 1255711 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c7e3b7c8a6772c18987bf308ded653caf1bae61db59199a5f00e8885e719be9d" } } ], "extra": [ 1, 182, 114, 188, 85, 101, 150, 92, 182, 60, 227, 211, 79, 114, 27, 37, 230, 194, 19, 138, 245, 11, 115, 125, 79, 155, 216, 217, 251, 26, 90, 201, 118, 2, 17, 0, 0, 0, 13, 108, 152, 170, 61, 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