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: a8c62d7a8e4fb25d783900f556615b82d079dfb6ba4e41bdb280843bd0a03240
Tx prefix hash: 3dd730259e1d01ca0efa2d88d0a01919c1eccda8ba1e322df9796587ea987ad3
Tx public key: 06a444f2d6b398555d8c96b35d066bcdc8e6bd56d98830c9174fcc895dd86449
| Timestamp: 1779718564 | Timestamp [UTC]: 2026-05-25 14:16:04 | Age [y:d:h:m:s]: 00:014:11:19:53 |
| Block: 1706 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 6180 | RingCT/type: yes/0 |
| Extra: 0106a444f2d6b398555d8c96b35d066bcdc8e6bd56d98830c9174fcc895dd86449020900000002ba6d17be00 | ||
1 output(s) for total of 35.070137215143 HMNY
| stealth address | amount | amount idx | tag |
| 00: 2fc670eb06cbc010c65c6394a00e0fdcd70e954194388a315176bc61b3486f6d | 35.070137215143 | 1877 of 0 | <24> |
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": 1766,
"vin": [ {
"gen": {
"height": 1706
}
}
],
"vout": [ {
"amount": 35070137215143,
"target": {
"tagged_key": {
"key": "2fc670eb06cbc010c65c6394a00e0fdcd70e954194388a315176bc61b3486f6d",
"view_tag": "24"
}
}
}
],
"extra": [ 1, 6, 164, 68, 242, 214, 179, 152, 85, 93, 140, 150, 179, 93, 6, 107, 205, 200, 230, 189, 86, 217, 136, 48, 201, 23, 79, 204, 137, 93, 216, 100, 73, 2, 9, 0, 0, 0, 2, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}