Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9e7db125f112d72b9bad933cc5821dccddc97b640b1168552d856d5476c7c08e

Tx prefix hash: cbb6efcd1cbbc1766261d24de11688d0fab9791a0491eae290abd49576920c4a
Tx public key: d3945b48852da4d0c167a0757e5c3c164520df44acd44cde5f995acb4104ab20
Timestamp: 1583440074 Timestamp [UCT]: 2020-03-05 20:27:54 Age [y:d:h:m:s]: 04:298:14:40:00
Block: 76797 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1108175 RingCT/type: yes/0
Extra: 01d3945b48852da4d0c167a0757e5c3c164520df44acd44cde5f995acb4104ab2002110000006a7adf42d3000000000000000000

1 output(s) for total of 341.617770237000 dcy

stealth address amount amount idx
00: ae0d2924b3513c9c575dc8721f6beb1b361f7c690f116ed0c46d8e49008a4704 341.617770237000 141414 of 0

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": 76807, "vin": [ { "gen": { "height": 76797 } } ], "vout": [ { "amount": 341617770237, "target": { "key": "ae0d2924b3513c9c575dc8721f6beb1b361f7c690f116ed0c46d8e49008a4704" } } ], "extra": [ 1, 211, 148, 91, 72, 133, 45, 164, 208, 193, 103, 160, 117, 126, 92, 60, 22, 69, 32, 223, 68, 172, 212, 76, 222, 95, 153, 90, 203, 65, 4, 171, 32, 2, 17, 0, 0, 0, 106, 122, 223, 66, 211, 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