Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 53fdce98fec6f1ba24951610031c52169618261614301dd8ed8ca1cd4f3c7159

Tx prefix hash: 00dd135b2b3a4bc16d9768e134cbacc532c020dafbc8dd4b94a94b392517cab9
Tx public key: 73a9d7b43dc6d0d43907d54cfe866629596ae4b2915cdc10d94a1b83c8bd824e
Timestamp: 1725237243 Timestamp [UCT]: 2024-09-02 00:34:03 Age [y:d:h:m:s]: 00:111:18:04:20
Block: 1100980 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 79953 RingCT/type: yes/0
Extra: 0173a9d7b43dc6d0d43907d54cfe866629596ae4b2915cdc10d94a1b83c8bd824e02110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 14732a53f0e36c9bdb50af79ff7d4658eb19adb1be2ebb741d254bbbfd496689 0.600000000000 1576961 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": 1100990, "vin": [ { "gen": { "height": 1100980 } } ], "vout": [ { "amount": 600000000, "target": { "key": "14732a53f0e36c9bdb50af79ff7d4658eb19adb1be2ebb741d254bbbfd496689" } } ], "extra": [ 1, 115, 169, 215, 180, 61, 198, 208, 212, 57, 7, 213, 76, 254, 134, 102, 41, 89, 106, 228, 178, 145, 92, 220, 16, 217, 74, 27, 131, 200, 189, 130, 78, 2, 17, 0, 0, 0, 1, 145, 225, 60, 4, 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