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: 7a876eabdb7da5dcc1367a3ea87fd0cbc1c01b139693c9a7283377efe8255848
Tx prefix hash: e1f72ba232496ca49db8fd39b02d1de52174f6ad6089ec55f7843f1c2493250d
Tx public key: 05879e06fb7fd5a4399e256ff7ed3e3f0cb2cb4d40cfebb0b1d165693ae73ed4
| Timestamp: 1780052485 | Timestamp [UTC]: 2026-05-29 11:01:25 | Age [y:d:h:m:s]: 00:010:13:45:22 |
| Block: 4415 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3471 | RingCT/type: yes/0 |
| Extra: 0105879e06fb7fd5a4399e256ff7ed3e3f0cb2cb4d40cfebb0b1d165693ae73ed402090000000826697be300 | ||
1 output(s) for total of 34.889396728480 HMNY
| stealth address | amount | amount idx | tag |
| 00: b3b70b52f96f084d2a4cff74eec9ed77495342c6c18fa1c93239d1adee1d1381 | 34.889396728480 | 5525 of 0 | <fc> |
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": 4475,
"vin": [ {
"gen": {
"height": 4415
}
}
],
"vout": [ {
"amount": 34889396728480,
"target": {
"tagged_key": {
"key": "b3b70b52f96f084d2a4cff74eec9ed77495342c6c18fa1c93239d1adee1d1381",
"view_tag": "fc"
}
}
}
],
"extra": [ 1, 5, 135, 158, 6, 251, 127, 213, 164, 57, 158, 37, 111, 247, 237, 62, 63, 12, 178, 203, 77, 64, 207, 235, 176, 177, 209, 101, 105, 58, 231, 62, 212, 2, 9, 0, 0, 0, 8, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}