Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5a83436384a664b997f19034b40f3fdd4ffe6d3b3e6aa397673f2605f1155a22

Tx prefix hash: a278253c19bab58aabba3ab90a92ec15b69748bbf581db4f7b0e80f7e1bf1aa7
Tx public key: 4bbd74d6e552fc9c0722301a80f147578358e6f7e07d9f8f81b0dc00187c29ef
Timestamp: 1732912122 Timestamp [UCT]: 2024-11-29 20:28:42 Age [y:d:h:m:s]: 00:130:14:39:22
Block: 1164502 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 93164 RingCT/type: yes/0
Extra: 014bbd74d6e552fc9c0722301a80f147578358e6f7e07d9f8f81b0dc00187c29ef0211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 60fde56fc80a86664430a5454b604fb3aa6d0d35f179a6a56d85555b430f8d2b 0.600000000000 1650175 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": 1164512, "vin": [ { "gen": { "height": 1164502 } } ], "vout": [ { "amount": 600000000, "target": { "key": "60fde56fc80a86664430a5454b604fb3aa6d0d35f179a6a56d85555b430f8d2b" } } ], "extra": [ 1, 75, 189, 116, 214, 229, 82, 252, 156, 7, 34, 48, 26, 128, 241, 71, 87, 131, 88, 230, 247, 224, 125, 159, 143, 129, 176, 220, 0, 24, 124, 41, 239, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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