Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8ff57898ae743f5e6f63a2dff4e56264f36e767a1c0392e774e25d61056d2c46

Tx prefix hash: b006fa6202f8fc2b96ac77b0f41914d32c9938d0309388826090457332300a56
Tx public key: cbc9dfcc5088ce690d35e1b442de0c7eacc3b3340bfe2e19f13a37cc87287b6c
Timestamp: 1736450002 Timestamp [UCT]: 2025-01-09 19:13:22 Age [y:d:h:m:s]: 00:066:17:18:15
Block: 1193787 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 47482 RingCT/type: yes/0
Extra: 01cbc9dfcc5088ce690d35e1b442de0c7eacc3b3340bfe2e19f13a37cc87287b6c021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0e0e829dcd47754a7cb3df946b240eb07ab5ef5b78b11576bc51f13de43f8987 0.600000000000 1680352 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": 1193797, "vin": [ { "gen": { "height": 1193787 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0e0e829dcd47754a7cb3df946b240eb07ab5ef5b78b11576bc51f13de43f8987" } } ], "extra": [ 1, 203, 201, 223, 204, 80, 136, 206, 105, 13, 53, 225, 180, 66, 222, 12, 126, 172, 195, 179, 52, 11, 254, 46, 25, 241, 58, 55, 204, 135, 40, 123, 108, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 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