Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0ab1b82be83b2d7b71570aca1c0bfa1a325d2f79b433382410e1e6e0390229ce

Tx prefix hash: dbbcba524f15edce81a679e88381db5e9efda4e9d9b1f15e35014b898425ee0e
Tx public key: 33bfb74b4e073e7cdadef7965dd0177b63342d0c5e3431b39cbafa773ca382d2
Timestamp: 1703387898 Timestamp [UCT]: 2023-12-24 03:18:18 Age [y:d:h:m:s]: 01:126:13:41:04
Block: 919828 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 351604 RingCT/type: yes/0
Extra: 0133bfb74b4e073e7cdadef7965dd0177b63342d0c5e3431b39cbafa773ca382d202110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 347e226998e7cc0dfe2a9f10530f096558426d8c1d3c462123e5c289104dd050 0.600000000000 1377506 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": 919838, "vin": [ { "gen": { "height": 919828 } } ], "vout": [ { "amount": 600000000, "target": { "key": "347e226998e7cc0dfe2a9f10530f096558426d8c1d3c462123e5c289104dd050" } } ], "extra": [ 1, 51, 191, 183, 75, 78, 7, 62, 124, 218, 222, 247, 150, 93, 208, 23, 123, 99, 52, 45, 12, 94, 52, 49, 179, 156, 186, 250, 119, 60, 163, 130, 210, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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