Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 565ee173c92a7c4f21a5e3f5f19ddda72a011274eb39f156ba82dcb59b5da34a

Tx prefix hash: a311b2ab5eda240dcd1c24a1c3a1f8661b3e52c7da0b10f4edb9c6a3ea05a709
Tx public key: 4cc0c5c945594d2988092f4375314bdbf6959dd5168e5dcae0e5e66ac2272196
Timestamp: 1731904865 Timestamp [UCT]: 2024-11-18 04:41:05 Age [y:d:h:m:s]: 00:124:07:18:03
Block: 1156161 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 88655 RingCT/type: yes/0
Extra: 014cc0c5c945594d2988092f4375314bdbf6959dd5168e5dcae0e5e66ac2272196021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b1cb94784760e6c35a3cca05f3cc40cb9e800be1da33119c00edd784c53fea62 0.600000000000 1641784 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": 1156171, "vin": [ { "gen": { "height": 1156161 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b1cb94784760e6c35a3cca05f3cc40cb9e800be1da33119c00edd784c53fea62" } } ], "extra": [ 1, 76, 192, 197, 201, 69, 89, 77, 41, 136, 9, 47, 67, 117, 49, 75, 219, 246, 149, 157, 213, 22, 142, 93, 202, 224, 229, 230, 106, 194, 39, 33, 150, 2, 17, 0, 0, 0, 3, 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