Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8760a0f95eef93d39f17bbd68ad911577103a86117747a768a53d260d31b6584

Tx prefix hash: c42b85b3b8806679ed40504b12eb76d51427d773d7bea027d13fcd596d6ac3a1
Tx public key: caf27da4d32cf3463da7a4f884ab0a92c3032bf4cf316bfce53e21f9c6245101
Timestamp: 1700140512 Timestamp [UCT]: 2023-11-16 13:15:12 Age [y:d:h:m:s]: 01:061:13:07:04
Block: 892912 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 305381 RingCT/type: yes/0
Extra: 01caf27da4d32cf3463da7a4f884ab0a92c3032bf4cf316bfce53e21f9c624510102110000000875e3f0e9000000000000000000

1 output(s) for total of 0.675168034000 dcy

stealth address amount amount idx
00: b95b6c6c19663e510361b46cfecad8cee8b6f33eaee743ed8af741d83273b0ac 0.675168034000 1349065 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": 892922, "vin": [ { "gen": { "height": 892912 } } ], "vout": [ { "amount": 675168034, "target": { "key": "b95b6c6c19663e510361b46cfecad8cee8b6f33eaee743ed8af741d83273b0ac" } } ], "extra": [ 1, 202, 242, 125, 164, 211, 44, 243, 70, 61, 167, 164, 248, 132, 171, 10, 146, 195, 3, 43, 244, 207, 49, 107, 252, 229, 62, 33, 249, 198, 36, 81, 1, 2, 17, 0, 0, 0, 8, 117, 227, 240, 233, 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