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: a27d1ec34e4060885f674bfdc455b0049136bf544c9250465b94a76fae395644
Tx prefix hash: 33202d5b2457443dca8f031ea377b877b7dfe34205314aac6dc2d560a2c2c72c
Tx public key: 9b1792df196ac716a4244a340eee07ec79b035aa07af1b72efa3299259d38e52
| Timestamp: 1779790926 | Timestamp [UTC]: 2026-05-26 10:22:06 | Age [y:d:h:m:s]: 00:013:14:24:41 |
| Block: 2226 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 5660 | RingCT/type: yes/0 |
| Extra: 019b1792df196ac716a4244a340eee07ec79b035aa07af1b72efa3299259d38e5202090000000226697be300 | ||
1 output(s) for total of 35.035371117016 HMNY
| stealth address | amount | amount idx | tag |
| 00: 6cc36d9988310ec8f89323e64898e71bfa20f23bdd91cd1a494190af17ba7a3a | 35.035371117016 | 2578 of 0 | <f4> |
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": 2286,
"vin": [ {
"gen": {
"height": 2226
}
}
],
"vout": [ {
"amount": 35035371117016,
"target": {
"tagged_key": {
"key": "6cc36d9988310ec8f89323e64898e71bfa20f23bdd91cd1a494190af17ba7a3a",
"view_tag": "f4"
}
}
}
],
"extra": [ 1, 155, 23, 146, 223, 25, 106, 199, 22, 164, 36, 74, 52, 14, 238, 7, 236, 121, 176, 53, 170, 7, 175, 27, 114, 239, 163, 41, 146, 89, 211, 142, 82, 2, 9, 0, 0, 0, 2, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}