Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c6740feaad4204d48bc86afcdc0a099730a97c26ecebf33e4539a4f448d95ae1

Tx prefix hash: b8a4397c22c7db9b966d5fd58db7e1e2dcd1d9c2acd6c16187c13112dcee28b2
Tx public key: e26c5cd35a9f3e55f5a32a7f3a74fcca9eb57f3b74d1d9f7052766ec5edce7ea
Timestamp: 1722555874 Timestamp [UCT]: 2024-08-01 23:44:34 Age [y:d:h:m:s]: 01:090:02:36:06
Block: 1078740 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 322885 RingCT/type: yes/0
Extra: 01e26c5cd35a9f3e55f5a32a7f3a74fcca9eb57f3b74d1d9f7052766ec5edce7ea021100000008e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 017b012ef7489b060ba5345814fbb979306d9fb31a8cb905bbc35cf26fe1109d 0.600000000000 1551397 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": 1078750, "vin": [ { "gen": { "height": 1078740 } } ], "vout": [ { "amount": 600000000, "target": { "key": "017b012ef7489b060ba5345814fbb979306d9fb31a8cb905bbc35cf26fe1109d" } } ], "extra": [ 1, 226, 108, 92, 211, 90, 159, 62, 85, 245, 163, 42, 127, 58, 116, 252, 202, 158, 181, 127, 59, 116, 209, 217, 247, 5, 39, 102, 236, 94, 220, 231, 234, 2, 17, 0, 0, 0, 8, 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