Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6941bad7e7ee61949bc144c6ebc1c0b2ce925cef779e623482d87d8c27556a20

Tx prefix hash: 834c0d42b469f786a55398da5c16519e9c45b794e7e1f4c6bd6d2a40b1bc2e84
Tx public key: 285ac4955d217d54e1a83f989366fad82b8d532f1ebab42a77348cae9172b471
Timestamp: 1704826129 Timestamp [UCT]: 2024-01-09 18:48:49 Age [y:d:h:m:s]: 01:088:09:50:21
Block: 931740 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 324283 RingCT/type: yes/0
Extra: 01285ac4955d217d54e1a83f989366fad82b8d532f1ebab42a77348cae9172b47102110000000b52d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a7848017ea840f246fe62954f742adf759178f3b5e806b9457cd42e8eb2347a8 0.600000000000 1389644 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": 931750, "vin": [ { "gen": { "height": 931740 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a7848017ea840f246fe62954f742adf759178f3b5e806b9457cd42e8eb2347a8" } } ], "extra": [ 1, 40, 90, 196, 149, 93, 33, 125, 84, 225, 168, 63, 152, 147, 102, 250, 216, 43, 141, 83, 47, 30, 186, 180, 42, 119, 52, 140, 174, 145, 114, 180, 113, 2, 17, 0, 0, 0, 11, 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