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: c02a71018d97fc206b4c203b5a4564ae983532ef5fb7992fffd5a96656518819
Tx prefix hash: 57869a42ff9895b66c81dbce49110744bbb68e4758ae2d68d6a7d211eb330a5b
Tx public key: 2c41f5ff69549aa426326e6cb6866fe98e57126d725447a72b24f8026ef8703b
| Timestamp: 1780687158 | Timestamp [UTC]: 2026-06-05 19:19:18 | Age [y:d:h:m:s]: 00:003:05:27:29 |
| Block: 5460 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2426 | RingCT/type: yes/0 |
| Extra: 012c41f5ff69549aa426326e6cb6866fe98e57126d725447a72b24f8026ef8703b020900000001e49593ff00 | ||
1 output(s) for total of 34.819925095846 HMNY
| stealth address | amount | amount idx | tag |
| 00: b686a4c70b47710d81ec585df2e942c87de73e840ee5c815eb7309dc319b1b51 | 34.819925095846 | 6899 of 0 | <6e> |
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": 5520,
"vin": [ {
"gen": {
"height": 5460
}
}
],
"vout": [ {
"amount": 34819925095846,
"target": {
"tagged_key": {
"key": "b686a4c70b47710d81ec585df2e942c87de73e840ee5c815eb7309dc319b1b51",
"view_tag": "6e"
}
}
}
],
"extra": [ 1, 44, 65, 245, 255, 105, 84, 154, 164, 38, 50, 110, 108, 182, 134, 111, 233, 142, 87, 18, 109, 114, 84, 71, 167, 43, 36, 248, 2, 110, 248, 112, 59, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}