Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8bc3fa0a3d9492c70dd808a489feddf8baf37d4b7d84e2307738b024e5eace95

Tx prefix hash: c91877a9663569bd8db99db4f6a90a54534bc83eaea37672cf1a8b9b558853cf
Tx public key: 8f5223f34af6eb93a08d45a79576907d47a3fd998f23bac7af37a3bec1cf4dfe
Timestamp: 1735073034 Timestamp [UCT]: 2024-12-24 20:43:54 Age [y:d:h:m:s]: 00:093:21:17:07
Block: 1182403 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 66879 RingCT/type: yes/0
Extra: 018f5223f34af6eb93a08d45a79576907d47a3fd998f23bac7af37a3bec1cf4dfe0211000000071f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1be6a6c011ce8daaf0b7ca72534c2afdbd1e5b39e1ffd2c3bc7789a9f1ce243d 0.600000000000 1668836 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": 1182413, "vin": [ { "gen": { "height": 1182403 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1be6a6c011ce8daaf0b7ca72534c2afdbd1e5b39e1ffd2c3bc7789a9f1ce243d" } } ], "extra": [ 1, 143, 82, 35, 243, 74, 246, 235, 147, 160, 141, 69, 167, 149, 118, 144, 125, 71, 163, 253, 153, 143, 35, 186, 199, 175, 55, 163, 190, 193, 207, 77, 254, 2, 17, 0, 0, 0, 7, 31, 10, 83, 235, 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