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: 54d036a69f9a55d117d854395790c6ffff5832f9c811fc42f5584b41c4348564
Tx prefix hash: 3c5dad6c731d5f2a2d44cf734ab88a40ae6f71266c291d362fd20072ea5f1203
Tx public key: b6a345496c54b6db8c5f59a6cf54ebedc569bdf8a9637cb79f81394514d9a8ee
| Timestamp: 1779921097 | Timestamp [UTC]: 2026-05-27 22:31:37 | Age [y:d:h:m:s]: 00:016:12:30:39 |
| Block: 3354 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 5391 | RingCT/type: yes/0 |
| Extra: 01b6a345496c54b6db8c5f59a6cf54ebedc569bdf8a9637cb79f81394514d9a8ee02090000000526697be300 | ||
1 output(s) for total of 34.960073850280 HMNY
| stealth address | amount | amount idx | tag |
| 00: 0b4ba51e19f535389660e6f49afbdfc769b0f9dd7f61d5b49b6c775f43b409d1 | 34.960073850280 | 4037 of 0 | <6b> |
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": 3414,
"vin": [ {
"gen": {
"height": 3354
}
}
],
"vout": [ {
"amount": 34960073850280,
"target": {
"tagged_key": {
"key": "0b4ba51e19f535389660e6f49afbdfc769b0f9dd7f61d5b49b6c775f43b409d1",
"view_tag": "6b"
}
}
}
],
"extra": [ 1, 182, 163, 69, 73, 108, 84, 182, 219, 140, 95, 89, 166, 207, 84, 235, 237, 197, 105, 189, 248, 169, 99, 124, 183, 159, 129, 57, 69, 20, 217, 168, 238, 2, 9, 0, 0, 0, 5, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}