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: 312778cc940d7c619c9ffd5b10c3de01621bd679d5d074acb9cdf429d1dc7c3d
Tx prefix hash: 28f81b9f1dea051b5c187fc763e260f9b561e15607ca2600d47371704f0d0adf
Tx public key: 39f7a0b40b0c8e8c9aee981042b7553b01f9ecaf88d46e2c2fb92c01be1f4837
| Timestamp: 1780979688 | Timestamp [UTC]: 2026-06-09 04:34:48 | Age [y:d:h:m:s]: 00:000:08:02:57 |
| Block: 8006 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 566 | RingCT/type: yes/0 |
| Extra: 0139f7a0b40b0c8e8c9aee981042b7553b01f9ecaf88d46e2c2fb92c01be1f4837020900000002e49593ff00 | ||
1 output(s) for total of 34.651245456675 HMNY
| stealth address | amount | amount idx | tag |
| 00: f18f31d44112ac86a5e750e59574fab91182df479e71a7a409de49195adee536 | 34.651245456675 | 9926 of 0 | <c0> |
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": 8066,
"vin": [ {
"gen": {
"height": 8006
}
}
],
"vout": [ {
"amount": 34651245456675,
"target": {
"tagged_key": {
"key": "f18f31d44112ac86a5e750e59574fab91182df479e71a7a409de49195adee536",
"view_tag": "c0"
}
}
}
],
"extra": [ 1, 57, 247, 160, 180, 11, 12, 142, 140, 154, 238, 152, 16, 66, 183, 85, 59, 1, 249, 236, 175, 136, 212, 110, 44, 47, 185, 44, 1, 190, 31, 72, 55, 2, 9, 0, 0, 0, 2, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}