Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5ab693bd858dd7267e938bb45a5ad72c3c1364e0dafaec3f4efa94a8fec0f7d7

Tx prefix hash: d330f116a88b03f3750579d5b8346cfeaa75004e87d23b1d0f87dae6fc7958bf
Tx public key: c0a163233812716a3a162c5173ee67bcf55ae8c837b5cc5c16127a8f71e0d9d8
Timestamp: 1719407061 Timestamp [UCT]: 2024-06-26 13:04:21 Age [y:d:h:m:s]: 00:263:22:12:38
Block: 1052631 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 188608 RingCT/type: yes/0
Extra: 01c0a163233812716a3a162c5173ee67bcf55ae8c837b5cc5c16127a8f71e0d9d80211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 776412ac5e57baf475eccc9f1faa6ccb1543ed77db62ca084dfe0e281bd9bf81 0.600000000000 1522962 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": 1052641, "vin": [ { "gen": { "height": 1052631 } } ], "vout": [ { "amount": 600000000, "target": { "key": "776412ac5e57baf475eccc9f1faa6ccb1543ed77db62ca084dfe0e281bd9bf81" } } ], "extra": [ 1, 192, 161, 99, 35, 56, 18, 113, 106, 58, 22, 44, 81, 115, 238, 103, 188, 245, 90, 232, 200, 55, 181, 204, 92, 22, 18, 122, 143, 113, 224, 217, 216, 2, 17, 0, 0, 0, 2, 0, 17, 5, 91, 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