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: 76ed547438ea363af06ff37a28a69c14d0fe93c10dc3d239b4dff7cc661b1f2c
Tx prefix hash: 8aa2d40200f0faedb8434f51d3bd952607b683b573873bf41e7901b49f0d1938
Tx public key: 8f331effe9549253d8ccf8366ed4ad3732c44d5dacadc5f95563dc75b2e86e8e
| Timestamp: 1780687208 | Timestamp [UTC]: 2026-06-05 19:20:08 | Age [y:d:h:m:s]: 00:007:15:42:08 |
| Block: 5467 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3278 | RingCT/type: yes/0 |
| Extra: 018f331effe9549253d8ccf8366ed4ad3732c44d5dacadc5f95563dc75b2e86e8e020900000001e49593ff00 | ||
1 output(s) for total of 34.819460202350 HMNY
| stealth address | amount | amount idx | tag |
| 00: 2c8026a7e357af812163081e2911592a09598398773195a4d1a72dad62161c09 | 34.819460202350 | 6906 of 0 | <8b> |
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": 5527,
"vin": [ {
"gen": {
"height": 5467
}
}
],
"vout": [ {
"amount": 34819460202350,
"target": {
"tagged_key": {
"key": "2c8026a7e357af812163081e2911592a09598398773195a4d1a72dad62161c09",
"view_tag": "8b"
}
}
}
],
"extra": [ 1, 143, 51, 30, 255, 233, 84, 146, 83, 216, 204, 248, 54, 110, 212, 173, 55, 50, 196, 77, 93, 172, 173, 197, 249, 85, 99, 220, 117, 178, 232, 110, 142, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}