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: 9b1bfdfc76d599b39e83fdc944dc586d6b837356c9f9a83bc7fb34403d3e1509
Tx prefix hash: 6579d980b5dd9945cf39b5533f2d817836cf22d44e0f1333132200c9960e2629
Tx public key: 3569d9c9dcf0cb2a21f80f2f4d4fd78063e098d3b0be886ad4fc2d90fd295192
| Timestamp: 1780049676 | Timestamp [UTC]: 2026-05-29 10:14:36 | Age [y:d:h:m:s]: 00:010:15:21:21 |
| Block: 4379 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3507 | RingCT/type: yes/0 |
| Extra: 013569d9c9dcf0cb2a21f80f2f4d4fd78063e098d3b0be886ad4fc2d90fd29519202090000000426697be300 | ||
1 output(s) for total of 34.891792477769 HMNY
| stealth address | amount | amount idx | tag |
| 00: 3ddd92a1113a636991c2e1fb8fc0737c04d4aa2f4bb1a5f241d46b97a3db5ebd | 34.891792477769 | 5478 of 0 | <a4> |
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": 4439,
"vin": [ {
"gen": {
"height": 4379
}
}
],
"vout": [ {
"amount": 34891792477769,
"target": {
"tagged_key": {
"key": "3ddd92a1113a636991c2e1fb8fc0737c04d4aa2f4bb1a5f241d46b97a3db5ebd",
"view_tag": "a4"
}
}
}
],
"extra": [ 1, 53, 105, 217, 201, 220, 240, 203, 42, 33, 248, 15, 47, 77, 79, 215, 128, 99, 224, 152, 211, 176, 190, 136, 106, 212, 252, 45, 144, 253, 41, 81, 146, 2, 9, 0, 0, 0, 4, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}