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: 70f00198d0b40a1c53fdf19f497a6f6886c83c8d16548ced3fea18326c1a3471
Tx prefix hash: ac41ef199e0a26b9fb2d55a4dac9ee02f83cafa8c6cc9d4ae309ac0202e8ec81
Tx public key: ff1357b3e3c4c36ea060313412e6f3f95ac3fcf276cea46d9bae6a1ca6cf29b1
| Timestamp: 1780066567 | Timestamp [UTC]: 2026-05-29 14:56:07 | Age [y:d:h:m:s]: 00:010:11:53:41 |
| Block: 4591 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3308 | RingCT/type: yes/0 |
| Extra: 01ff1357b3e3c4c36ea060313412e6f3f95ac3fcf276cea46d9bae6a1ca6cf29b102090000000126697be300 | ||
1 output(s) for total of 34.877686544143 HMNY
| stealth address | amount | amount idx | tag |
| 00: c2f938ec164c2785bd501e769a7f64704f6cf763a0df46ac9ba925d8bec14f34 | 34.877686544143 | 5763 of 0 | <6a> |
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": 4651,
"vin": [ {
"gen": {
"height": 4591
}
}
],
"vout": [ {
"amount": 34877686544143,
"target": {
"tagged_key": {
"key": "c2f938ec164c2785bd501e769a7f64704f6cf763a0df46ac9ba925d8bec14f34",
"view_tag": "6a"
}
}
}
],
"extra": [ 1, 255, 19, 87, 179, 227, 196, 195, 110, 160, 96, 49, 52, 18, 230, 243, 249, 90, 195, 252, 242, 118, 206, 164, 109, 155, 174, 106, 28, 166, 207, 41, 177, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}