Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c5a88725aa8382085ed7686c7f0850a1099d98c403b80c28c0bfd807bd24a858

Tx prefix hash: ad5ecb3f2e85a664ddad2258ee4eeedc68c936ec7e644ab151c96657d55a0dc6
Tx public key: 56b57a1fa45c07b51363c3acb728306f1bc7c28c41028c8ca2e5b1e235924384
Timestamp: 1705285044 Timestamp [UCT]: 2024-01-15 02:17:24 Age [y:d:h:m:s]: 01:116:09:55:43
Block: 935532 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 344331 RingCT/type: yes/0
Extra: 0156b57a1fa45c07b51363c3acb728306f1bc7c28c41028c8ca2e5b1e23592438402110000000552d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2ce58e111c40673ac0b68bcfc9f34a9104c1703af2e33f8e3d96ffddde318231 0.600000000000 1393548 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": 935542, "vin": [ { "gen": { "height": 935532 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2ce58e111c40673ac0b68bcfc9f34a9104c1703af2e33f8e3d96ffddde318231" } } ], "extra": [ 1, 86, 181, 122, 31, 164, 92, 7, 181, 19, 99, 195, 172, 183, 40, 48, 111, 27, 199, 194, 140, 65, 2, 140, 140, 162, 229, 177, 226, 53, 146, 67, 132, 2, 17, 0, 0, 0, 5, 82, 212, 126, 148, 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