Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e6880169e87d48c97bb3962240690225896277cd738920dad9d38da5aeb05a46

Tx prefix hash: 302fdaf05e0c45850665a219f2ef4a9f27e93ef2fddcc47135fb2297c0a251c3
Tx public key: a0bb43070f0aa4ce36ba55fcdbbb6322dbb8418510cb525c4e0a0c46913e73a8
Timestamp: 1576643311 Timestamp [UCT]: 2019-12-18 04:28:31 Age [y:d:h:m:s]: 04:338:06:58:39
Block: 28147 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1128932 RingCT/type: yes/0
Extra: 01a0bb43070f0aa4ce36ba55fcdbbb6322dbb8418510cb525c4e0a0c46913e73a802110000003aad433a0b000000000000000000

1 output(s) for total of 495.151580487000 dcy

stealth address amount amount idx
00: 4564a26a2993b3b434b6bac478aa85fb591d7cf83b92926109c5cfac2903c7f8 495.151580487000 46677 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": 28157, "vin": [ { "gen": { "height": 28147 } } ], "vout": [ { "amount": 495151580487, "target": { "key": "4564a26a2993b3b434b6bac478aa85fb591d7cf83b92926109c5cfac2903c7f8" } } ], "extra": [ 1, 160, 187, 67, 7, 15, 10, 164, 206, 54, 186, 85, 252, 219, 187, 99, 34, 219, 184, 65, 133, 16, 203, 82, 92, 78, 10, 12, 70, 145, 62, 115, 168, 2, 17, 0, 0, 0, 58, 173, 67, 58, 11, 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