Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 89c5b6d12c60ac3030ca72f5b9ba919e4815a380eebd047c4b18167e4dcac65e

Tx prefix hash: c4fccca085b206b8b2f0a2e54d2dc8d0e17cb0f596d33bb0d1d348101d71c7f2
Tx public key: 7ec4fdefdf55222f412d518850de9ed394b3405c0d181a7f8cb96f3814c31fa1
Timestamp: 1721758791 Timestamp [UCT]: 2024-07-23 18:19:51 Age [y:d:h:m:s]: 01:111:15:31:45
Block: 1072126 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 338306 RingCT/type: yes/0
Extra: 017ec4fdefdf55222f412d518850de9ed394b3405c0d181a7f8cb96f3814c31fa102110000000be914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4a4b8be219f2aab79ce2ea24609f535fe64bf4d7205a629829a854be0e915872 0.600000000000 1544577 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": 1072136, "vin": [ { "gen": { "height": 1072126 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4a4b8be219f2aab79ce2ea24609f535fe64bf4d7205a629829a854be0e915872" } } ], "extra": [ 1, 126, 196, 253, 239, 223, 85, 34, 47, 65, 45, 81, 136, 80, 222, 158, 211, 148, 179, 64, 92, 13, 24, 26, 127, 140, 185, 111, 56, 20, 195, 31, 161, 2, 17, 0, 0, 0, 11, 233, 20, 221, 21, 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