Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cc6b4a9bfe36136103bda4e97f4a45ab70ca9444cccea9a1158ec45042084d00

Tx prefix hash: 7b747cbd182e5921997330a84c53c3fdb9e21a931bfbcd7242df81b6c21c5036
Tx public key: c2c15233f7dc69c37b3e7eb44031938ec757018610655b16d0ceb82c33dc7bf8
Timestamp: 1586249315 Timestamp [UCT]: 2020-04-07 08:48:35 Age [y:d:h:m:s]: 04:266:01:22:17
Block: 92042 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1092901 RingCT/type: yes/0
Extra: 01c2c15233f7dc69c37b3e7eb44031938ec757018610655b16d0ceb82c33dc7bf802110000000286362411000000000000000000

1 output(s) for total of 304.107700870000 dcy

stealth address amount amount idx
00: 465a80e0a62a5cbbc9a93004ccb62ce0b907b179d335ee2a69ee70ff6e56f413 304.107700870000 164362 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": 92052, "vin": [ { "gen": { "height": 92042 } } ], "vout": [ { "amount": 304107700870, "target": { "key": "465a80e0a62a5cbbc9a93004ccb62ce0b907b179d335ee2a69ee70ff6e56f413" } } ], "extra": [ 1, 194, 193, 82, 51, 247, 220, 105, 195, 123, 62, 126, 180, 64, 49, 147, 142, 199, 87, 1, 134, 16, 101, 91, 22, 208, 206, 184, 44, 51, 220, 123, 248, 2, 17, 0, 0, 0, 2, 134, 54, 36, 17, 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