Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9270eac13d5ccce1ae178a415f966ea7aeb1c59d0659babb604ee90288c10a7e

Tx prefix hash: 4f6a0a3c0e17f2541866a8eb053ca32cb4876f047c153c2f5ac724dd0e16e788
Tx public key: 075728286cc9a12713635d7e14eacb03f8570629ea4f901f198fcce2edf35af9
Timestamp: 1688692420 Timestamp [UCT]: 2023-07-07 01:13:40 Age [y:d:h:m:s]: 01:311:20:07:27
Block: 798260 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 484030 RingCT/type: yes/0
Extra: 01075728286cc9a12713635d7e14eacb03f8570629ea4f901f198fcce2edf35af902110000000375e3f0e9000000000000000000

1 output(s) for total of 1.390059464000 dcy

stealth address amount amount idx
00: 9cc9b99d87674015b18acc5ab8ba1eaf4ee94f9221da517c7bff14501a57a814 1.390059464000 1249189 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": 798270, "vin": [ { "gen": { "height": 798260 } } ], "vout": [ { "amount": 1390059464, "target": { "key": "9cc9b99d87674015b18acc5ab8ba1eaf4ee94f9221da517c7bff14501a57a814" } } ], "extra": [ 1, 7, 87, 40, 40, 108, 201, 161, 39, 19, 99, 93, 126, 20, 234, 203, 3, 248, 87, 6, 41, 234, 79, 144, 31, 25, 143, 204, 226, 237, 243, 90, 249, 2, 17, 0, 0, 0, 3, 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