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: bacbe973b9ddfac6134d14826c1c4aed5f8ec9905c061be4c0327c570f834c9a
Tx prefix hash: ecc983f5d028b9708303cc6264687248b87db8ba3b4ce04a1cb4efe8484ccc31
Tx public key: 2144ae1dcf16548d4ff5b7860ed5713314754974a27ba91b8eef10d179967354
| Timestamp: 1779476490 | Timestamp [UTC]: 2026-05-22 19:01:30 | Age [y:d:h:m:s]: 00:017:07:48:18 |
| Block: 615 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 7284 | RingCT/type: yes/0 |
| Extra: 012144ae1dcf16548d4ff5b7860ed5713314754974a27ba91b8eef10d17996735402090000000293369e7d00 | ||
1 output(s) for total of 35.143191325527 HMNY
| stealth address | amount | amount idx | tag |
| 00: 0f2d1f81433b14f7eddbdc42c3643d7b8359e49989ef4f024215fce0bd0d05b9 | 35.143191325527 | 637 of 0 | <d0> |
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": 675,
"vin": [ {
"gen": {
"height": 615
}
}
],
"vout": [ {
"amount": 35143191325527,
"target": {
"tagged_key": {
"key": "0f2d1f81433b14f7eddbdc42c3643d7b8359e49989ef4f024215fce0bd0d05b9",
"view_tag": "d0"
}
}
}
],
"extra": [ 1, 33, 68, 174, 29, 207, 22, 84, 141, 79, 245, 183, 134, 14, 213, 113, 51, 20, 117, 73, 116, 162, 123, 169, 27, 142, 239, 16, 209, 121, 150, 115, 84, 2, 9, 0, 0, 0, 2, 147, 54, 158, 125, 0
],
"rct_signatures": {
"type": 0
}
}