Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c34c192877c3ed60a494a56dbc95dd7fc3e1c0707ae1ad324330f06e51173af6

Tx prefix hash: 6aad42dca6a4a11623526715a4ad52235a74fb34a929085fd0c3473ce8c53d6c
Tx public key: 1b9fe1f46eacc5d669bbb7fc0b652af68b8ad72bd4d7ad3b28aaea385b0e19ab
Timestamp: 1764252424 Timestamp [UCT]: 2025-11-27 14:07:04 Age [y:d:h:m:s]: 00:026:03:50:40
Block: 1421305 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 18722 RingCT/type: yes/0
Extra: 011b9fe1f46eacc5d669bbb7fc0b652af68b8ad72bd4d7ad3b28aaea385b0e19ab02110000000143b50471000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f746e67504ef54b196e0fe60609db6f702fd62e490dec0996c4d4c3265644dd8 0.600000000000 1909862 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": 1421315, "vin": [ { "gen": { "height": 1421305 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f746e67504ef54b196e0fe60609db6f702fd62e490dec0996c4d4c3265644dd8" } } ], "extra": [ 1, 27, 159, 225, 244, 110, 172, 197, 214, 105, 187, 183, 252, 11, 101, 42, 246, 139, 138, 215, 43, 212, 215, 173, 59, 40, 170, 234, 56, 91, 14, 25, 171, 2, 17, 0, 0, 0, 1, 67, 181, 4, 113, 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