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: 892a55115c034ed270f730bc072532ce683733efbc3b723c17fad7d2eb54e1f6
Tx prefix hash: 0df29c3e7d1b7f56511515856e20cf0c14271cca75c550db8b2b0d562f78009c
Tx public key: 071cbb5f75e60f860604bff41ea4ecb7c46134a5127ad8f80577d804a066ec69
| Timestamp: 1780897175 | Timestamp [UTC]: 2026-06-08 05:39:35 | Age [y:d:h:m:s]: 00:000:17:39:18 |
| Block: 7773 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 113 | RingCT/type: yes/0 |
| Extra: 01071cbb5f75e60f860604bff41ea4ecb7c46134a5127ad8f80577d804a066ec690209000000024a728a4c00 | ||
1 output(s) for total of 34.671671531039 HMNY
| stealth address | amount | amount idx | tag |
| 00: ed46dc29e432ce7457066204336cfc41cfd9fe770d929cfc76a392bc88850b3c | 34.671671531039 | 9631 of 0 | <ea> |
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": 7833,
"vin": [ {
"gen": {
"height": 7773
}
}
],
"vout": [ {
"amount": 34671671531039,
"target": {
"tagged_key": {
"key": "ed46dc29e432ce7457066204336cfc41cfd9fe770d929cfc76a392bc88850b3c",
"view_tag": "ea"
}
}
}
],
"extra": [ 1, 7, 28, 187, 95, 117, 230, 15, 134, 6, 4, 191, 244, 30, 164, 236, 183, 196, 97, 52, 165, 18, 122, 216, 248, 5, 119, 216, 4, 160, 102, 236, 105, 2, 9, 0, 0, 0, 2, 74, 114, 138, 76, 0
],
"rct_signatures": {
"type": 0
}
}