Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 543f895524f91de28643c810d263fefbe2b236d093eb23cd2aab2d7387b9953c

Tx prefix hash: acbf145ea68ebecb33ec51e79e1fb2203e04550f761168acc9ce1580234e8adc
Tx public key: 543262abfce4fa135faba128df8fed7b28ba16a78c51fe3ac084ebea5e26b9e3
Timestamp: 1726879812 Timestamp [UCT]: 2024-09-21 00:50:12 Age [y:d:h:m:s]: 00:109:02:33:32
Block: 1114592 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 78012 RingCT/type: yes/0
Extra: 01543262abfce4fa135faba128df8fed7b28ba16a78c51fe3ac084ebea5e26b9e30211000000012c3a34dc000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a9d4dce54c7523b12c6762ba09c7d30a65f9c4b9bc820e43821d3422cd8c5b27 0.600000000000 1594429 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": 1114602, "vin": [ { "gen": { "height": 1114592 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a9d4dce54c7523b12c6762ba09c7d30a65f9c4b9bc820e43821d3422cd8c5b27" } } ], "extra": [ 1, 84, 50, 98, 171, 252, 228, 250, 19, 95, 171, 161, 40, 223, 143, 237, 123, 40, 186, 22, 167, 140, 81, 254, 58, 192, 132, 235, 234, 94, 38, 185, 227, 2, 17, 0, 0, 0, 1, 44, 58, 52, 220, 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