Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c59aeb1154e99f9a3ce56afacdb0b2896bed6b4603a79f7476a294be9e9660ec

Tx prefix hash: 1598867af6c4e6ce8cc1e3d70fef30d843b97cde14054d7a79a328038fa875c7
Tx public key: 5634075da4cde88f8868876d1234b9c101a6ff0239a8e87c585549c979b4c3c9
Timestamp: 1646570376 Timestamp [UCT]: 2022-03-06 12:39:36 Age [y:d:h:m:s]: 02:292:14:28:18
Block: 452555 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 728636 RingCT/type: yes/0
Extra: 015634075da4cde88f8868876d1234b9c101a6ff0239a8e87c585549c979b4c3c9021100000005d3fcec30000000000000000000

1 output(s) for total of 19.431113811000 dcy

stealth address amount amount idx
00: aec9f3efaa30f2ca82c64478aa9983918047c4a813a3f5d8535c6e443f84f7b2 19.431113811000 867888 of 0

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": 452565, "vin": [ { "gen": { "height": 452555 } } ], "vout": [ { "amount": 19431113811, "target": { "key": "aec9f3efaa30f2ca82c64478aa9983918047c4a813a3f5d8535c6e443f84f7b2" } } ], "extra": [ 1, 86, 52, 7, 93, 164, 205, 232, 143, 136, 104, 135, 109, 18, 52, 185, 193, 1, 166, 255, 2, 57, 168, 232, 124, 88, 85, 73, 201, 121, 180, 195, 201, 2, 17, 0, 0, 0, 5, 211, 252, 236, 48, 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