For RingCT transactions, outputs' amounts are also decoded
Tx private key can be obtained using get_tx_key
command in hashmonkey-wallet-cli command line tool
Tx hash: a7bc7017e3be28c6bef03ccd63e06740a1fabc3640292d5284543fc78dd6e23f
Tx prefix hash: 82a18886282ed4c3c8870b6d504b6c4fd837e61f025cf96b7fe9a3ae9e5e960e
Tx public key: dbfc66e08b3a93f4c21514a62ff5edfbc5fbd7a0d2cbfc4dd9a9d7de3ae387b7
| Timestamp: 1780978847 | Timestamp [UTC]: 2026-06-09 04:20:47 | Age [y:d:h:m:s]: 00:000:08:16:58 |
| Block: 7992 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 580 | RingCT/type: yes/0 |
| Extra: 01dbfc66e08b3a93f4c21514a62ff5edfbc5fbd7a0d2cbfc4dd9a9d7de3ae387b7020900000001e49593ff00 | ||
1 output(s) for total of 34.652170757990 HMNY
| stealth address | amount | amount idx | tag |
| 00: 3893da45293e5c518357cf712cb401bf51fd03d4203e941fca878c553f1d3686 | 34.652170757990 | 9910 of 0 | <c1> |
Check which outputs belong to given HMNY 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 HMNY in this transaction
Tx private key can be obtained using get_tx_key
command in hashmonkey-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": 8052,
"vin": [ {
"gen": {
"height": 7992
}
}
],
"vout": [ {
"amount": 34652170757990,
"target": {
"tagged_key": {
"key": "3893da45293e5c518357cf712cb401bf51fd03d4203e941fca878c553f1d3686",
"view_tag": "c1"
}
}
}
],
"extra": [ 1, 219, 252, 102, 224, 139, 58, 147, 244, 194, 21, 20, 166, 47, 245, 237, 251, 197, 251, 215, 160, 210, 203, 252, 77, 217, 169, 215, 222, 58, 227, 135, 183, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}