Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b785afc3566f60c12e5316195912b0c700d3d91e47ada1cc89b9b6c1ab7f5c98

Tx prefix hash: aa48051b31f176663ce4e5ed07ff7de612ddbc25b612b6cdcff5530b28c623ac
Tx public key: 7789bf3680000f49fc097584e7a09d9bc6dece914a136f0f3c73aa8888dcd934
Timestamp: 1685086994 Timestamp [UCT]: 2023-05-26 07:43:14 Age [y:d:h:m:s]: 01:298:03:58:33
Block: 768353 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 474323 RingCT/type: yes/0
Extra: 017789bf3680000f49fc097584e7a09d9bc6dece914a136f0f3c73aa8888dcd93402110000000133af99f4000000000000000000

1 output(s) for total of 1.746335686000 dcy

stealth address amount amount idx
00: dfcf8c44e7928421075b6ef8443e06c0a53c4b6c92d0c09a603cd65d9ae28d57 1.746335686000 1217548 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": 768363, "vin": [ { "gen": { "height": 768353 } } ], "vout": [ { "amount": 1746335686, "target": { "key": "dfcf8c44e7928421075b6ef8443e06c0a53c4b6c92d0c09a603cd65d9ae28d57" } } ], "extra": [ 1, 119, 137, 191, 54, 128, 0, 15, 73, 252, 9, 117, 132, 231, 160, 157, 155, 198, 222, 206, 145, 74, 19, 111, 15, 60, 115, 170, 136, 136, 220, 217, 52, 2, 17, 0, 0, 0, 1, 51, 175, 153, 244, 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