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: 8cc7cc3e058b11c0338d0b7a3f1f22e13e4c13f83c5b25b4ce1af6cfa4642cc1
Tx prefix hash: 0221cb41666522d63a6efbe4d3f90d645c945b45c79216fdbe35a7a29e44c7d7
Tx public key: 6da8e3ad6570d13465c34713159f913948908269e4d45791443116f147104f76
| Timestamp: 1780386421 | Timestamp [UTC]: 2026-06-02 07:47:01 | Age [y:d:h:m:s]: 00:006:18:53:35 |
| Block: 5180 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2717 | RingCT/type: yes/0 |
| Extra: 016da8e3ad6570d13465c34713159f913948908269e4d45791443116f147104f7602090000000426697be300 | ||
1 output(s) for total of 34.838525926328 HMNY
| stealth address | amount | amount idx | tag |
| 00: 36368070bef0ab0647ca39191d68259aace4c4b007279706d7155a62701775e6 | 34.838525926328 | 6559 of 0 | <68> |
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": 5240,
"vin": [ {
"gen": {
"height": 5180
}
}
],
"vout": [ {
"amount": 34838525926328,
"target": {
"tagged_key": {
"key": "36368070bef0ab0647ca39191d68259aace4c4b007279706d7155a62701775e6",
"view_tag": "68"
}
}
}
],
"extra": [ 1, 109, 168, 227, 173, 101, 112, 209, 52, 101, 195, 71, 19, 21, 159, 145, 57, 72, 144, 130, 105, 228, 212, 87, 145, 68, 49, 22, 241, 71, 16, 79, 118, 2, 9, 0, 0, 0, 4, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}