Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7b49c98516a356dbb76a5313a8af384376546291187f58bc50d478cd8e466085

Tx prefix hash: 5e24b4b78bef18d3951992b66d3c5f9b83e2a3eec329a9eef808154a7700f5ae
Tx public key: 52df74571eaeeeca1be3b70cc9a76c8b77c7c9338843b5972742f811bd6875a9
Timestamp: 1700620776 Timestamp [UCT]: 2023-11-22 02:39:36 Age [y:d:h:m:s]: 01:181:18:36:38
Block: 896888 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 391133 RingCT/type: yes/0
Extra: 0152df74571eaeeeca1be3b70cc9a76c8b77c7c9338843b5972742f811bd6875a902110000000375e3f0e9000000000000000000

1 output(s) for total of 0.654994613000 dcy

stealth address amount amount idx
00: fa20ddbaae46842791162285dc510f8e75c35ff01048dbf3f0a21a840dc958f3 0.654994613000 1353235 of 0

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": 896898, "vin": [ { "gen": { "height": 896888 } } ], "vout": [ { "amount": 654994613, "target": { "key": "fa20ddbaae46842791162285dc510f8e75c35ff01048dbf3f0a21a840dc958f3" } } ], "extra": [ 1, 82, 223, 116, 87, 30, 174, 238, 202, 27, 227, 183, 12, 201, 167, 108, 139, 119, 199, 201, 51, 136, 67, 181, 151, 39, 66, 248, 17, 189, 104, 117, 169, 2, 17, 0, 0, 0, 3, 117, 227, 240, 233, 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