Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c4ba02b2a02b5e014cb3a8a6a4c20782693443d008827b0a599838a3774fd177

Tx prefix hash: b9143e8e0840c8f20cd46c77d75f675eea37022c76ac7f0391ec6c5932a205f0
Tx public key: a868c8c28baeef93c8f9ebc151662f11430ee8ecd7656b84c504843db5a4f92d
Timestamp: 1705727720 Timestamp [UCT]: 2024-01-20 05:15:20 Age [y:d:h:m:s]: 01:292:07:02:37
Block: 939204 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 467720 RingCT/type: yes/0
Extra: 01a868c8c28baeef93c8f9ebc151662f11430ee8ecd7656b84c504843db5a4f92d0211000000057a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4e9d4c420b67bafc4eb086a6c8fa324d6907f0713df74abacf40dec488dffa07 0.600000000000 1397292 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": 939214, "vin": [ { "gen": { "height": 939204 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4e9d4c420b67bafc4eb086a6c8fa324d6907f0713df74abacf40dec488dffa07" } } ], "extra": [ 1, 168, 104, 200, 194, 139, 174, 239, 147, 200, 249, 235, 193, 81, 102, 47, 17, 67, 14, 232, 236, 215, 101, 107, 132, 197, 4, 132, 61, 181, 164, 249, 45, 2, 17, 0, 0, 0, 5, 122, 156, 244, 199, 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