Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2a4e86e86de4968cf9a4e3c0d8a12a2bcaccc42b25201d16924e045231f244d7

Tx prefix hash: b77cd2e80ff5d9e0647602436cab9a53d5042e2547827b7ac1e0583350bc58b1
Tx public key: 1786756336dd6af36ecbac3c5bd5b3705fc1bc585600188d15b4737ce663d3c3
Timestamp: 1707841141 Timestamp [UCT]: 2024-02-13 16:19:01 Age [y:d:h:m:s]: 01:052:20:46:01
Block: 956742 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 298821 RingCT/type: yes/0
Extra: 011786756336dd6af36ecbac3c5bd5b3705fc1bc585600188d15b4737ce663d3c30211000000057a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4f5be4a00a0f3fcddc577013d4e23243b2a7aa7c0bcc4c65e0bf18e864a81fe7 0.600000000000 1416052 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": 956752, "vin": [ { "gen": { "height": 956742 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4f5be4a00a0f3fcddc577013d4e23243b2a7aa7c0bcc4c65e0bf18e864a81fe7" } } ], "extra": [ 1, 23, 134, 117, 99, 54, 221, 106, 243, 110, 203, 172, 60, 91, 213, 179, 112, 95, 193, 188, 88, 86, 0, 24, 141, 21, 180, 115, 124, 230, 99, 211, 195, 2, 17, 0, 0, 0, 5, 122, 156, 244, 199, 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