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: b80562b126b946b6af54e1122f655d65358d87524d3f03da938fbd4417302094
Tx prefix hash: 6d00c6c20e8a5b910c4e3740c7b7b28a6fe83b1dfc1c50a77507ddf42cfdf02f
Tx public key: 57a47ce682906144001b358b8251e74caf6640c1ed651abc2d499141a4b6a524
| Timestamp: 1780131177 | Timestamp [UTC]: 2026-05-30 08:52:57 | Age [y:d:h:m:s]: 00:009:14:25:56 |
| Block: 4937 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2949 | RingCT/type: yes/0 |
| Extra: 0157a47ce682906144001b358b8251e74caf6640c1ed651abc2d499141a4b6a52402090000000126697be300 | ||
1 output(s) for total of 34.854676843496 HMNY
| stealth address | amount | amount idx | tag |
| 00: fa8b0a14576092620f085dee54602c3c51b09a7d35a5b55885a4f9de866ee960 | 34.854676843496 | 6272 of 0 | <90> |
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": 4997,
"vin": [ {
"gen": {
"height": 4937
}
}
],
"vout": [ {
"amount": 34854676843496,
"target": {
"tagged_key": {
"key": "fa8b0a14576092620f085dee54602c3c51b09a7d35a5b55885a4f9de866ee960",
"view_tag": "90"
}
}
}
],
"extra": [ 1, 87, 164, 124, 230, 130, 144, 97, 68, 0, 27, 53, 139, 130, 81, 231, 76, 175, 102, 64, 193, 237, 101, 26, 188, 45, 73, 145, 65, 164, 182, 165, 36, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}