Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0f11c57e51cd61790983c7dacf852b71ef2944339ef245ae28ce6faa4b960b9d

Tx prefix hash: 48dfd9d9388b51ee3b278de6a0ba510507da49d6568526d3cce3b8e3bb33be5c
Tx public key: 68493cf5e5fb46677e26ec00341d8b1e8473c7779cea7aaac8ceda2e0ecc2a7c
Timestamp: 1732405962 Timestamp [UCT]: 2024-11-23 23:52:42 Age [y:d:h:m:s]: 00:127:23:05:52
Block: 1160309 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 91264 RingCT/type: yes/0
Extra: 0168493cf5e5fb46677e26ec00341d8b1e8473c7779cea7aaac8ceda2e0ecc2a7c021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ae74b819f211a1a9c536c1600d650b5b52d628b7ddfa87195ce8c2f41994fc6a 0.600000000000 1645954 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": 1160319, "vin": [ { "gen": { "height": 1160309 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ae74b819f211a1a9c536c1600d650b5b52d628b7ddfa87195ce8c2f41994fc6a" } } ], "extra": [ 1, 104, 73, 60, 245, 229, 251, 70, 103, 126, 38, 236, 0, 52, 29, 139, 30, 132, 115, 199, 119, 156, 234, 122, 170, 200, 206, 218, 46, 14, 204, 42, 124, 2, 17, 0, 0, 0, 2, 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