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: 600f84b20cbed24d35e633266a2f1fa62bd97b03ae610ef112aca2b5e1733f1a
Tx prefix hash: 93c55e8e166ef2e5acb5f3c6980d26c3de84e0c55e5f8d639d31f9d8ddb70e11
Tx public key: 6f74c014605c0b7488f3f7fdafba5219b7c6ca03e25080d67ff8935aaab767be
| Timestamp: 1779871677 | Timestamp [UTC]: 2026-05-27 08:47:57 | Age [y:d:h:m:s]: 00:012:16:48:00 |
| Block: 2819 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 5067 | RingCT/type: yes/0 |
| Extra: 016f74c014605c0b7488f3f7fdafba5219b7c6ca03e25080d67ff8935aaab767be02090000000126697be300 | ||
1 output(s) for total of 34.995766453399 HMNY
| stealth address | amount | amount idx | tag |
| 00: 2c937a3e83922f07faf340b8a3d3c15c39145ab3a635580673df475ff2ff3b2d | 34.995766453399 | 3335 of 0 | <b1> |
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": 2879,
"vin": [ {
"gen": {
"height": 2819
}
}
],
"vout": [ {
"amount": 34995766453399,
"target": {
"tagged_key": {
"key": "2c937a3e83922f07faf340b8a3d3c15c39145ab3a635580673df475ff2ff3b2d",
"view_tag": "b1"
}
}
}
],
"extra": [ 1, 111, 116, 192, 20, 96, 92, 11, 116, 136, 243, 247, 253, 175, 186, 82, 25, 183, 198, 202, 3, 226, 80, 128, 214, 127, 248, 147, 90, 170, 183, 103, 190, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}