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: 0fbb3ed6985e501864716cd437abc54b7a67ca7ab10b69e1ca78245603fb5916
Tx prefix hash: 8423e14ba4b945a22120e156f50e76691d97bdc86c048da4da606b8d825a39a2
Tx public key: c8cb1ba708c9805ff999a7e33b3ecf87fa75d481f0aec461181c92e7cea6017e
| Timestamp: 1781003689 | Timestamp [UTC]: 2026-06-09 11:14:49 | Age [y:d:h:m:s]: 00:006:05:28:25 |
| Block: 8493 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 252 | RingCT/type: yes/0 |
| Extra: 01c8cb1ba708c9805ff999a7e33b3ecf87fa75d481f0aec461181c92e7cea6017e020900000001e49593ff00 | ||
1 output(s) for total of 34.619073563451 HMNY
| stealth address | amount | amount idx | tag |
| 00: b2c78f9498486198908c45307f7977e5b0df059ae43179e5d069424b33f45a5e | 34.619073563451 | 10493 of 0 | <02> |
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": 8553,
"vin": [ {
"gen": {
"height": 8493
}
}
],
"vout": [ {
"amount": 34619073563451,
"target": {
"tagged_key": {
"key": "b2c78f9498486198908c45307f7977e5b0df059ae43179e5d069424b33f45a5e",
"view_tag": "02"
}
}
}
],
"extra": [ 1, 200, 203, 27, 167, 8, 201, 128, 95, 249, 153, 167, 227, 59, 62, 207, 135, 250, 117, 212, 129, 240, 174, 196, 97, 24, 28, 146, 231, 206, 166, 1, 126, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}