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: 02b8e73e3a2fd24fc914dd0812d19118199fcf2122a8473b8b8c5ebc654231c5
Tx prefix hash: 7554ee927b5b3ef556056f5faebbffb0416e57807cc0ef7450b344d7a59bd81d
Tx public key: 4d3470d2cef762b577b9c03bf95633b32dd3c95a6c65022f364cfd6862b7f1d3
| Timestamp: 1780841983 | Timestamp [UTC]: 2026-06-07 14:19:43 | Age [y:d:h:m:s]: 00:001:12:30:05 |
| Block: 7474 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 425 | RingCT/type: yes/0 |
| Extra: 014d3470d2cef762b577b9c03bf95633b32dd3c95a6c65022f364cfd6862b7f1d3020900000002e49593ff00 | ||
1 output(s) for total of 34.694647882353 HMNY
| stealth address | amount | amount idx | tag |
| 00: 62572e2a11bcce71bf147c6210c5134826134bda0df618abfa3c0e705fa01cbe | 34.694647882353 | 9206 of 0 | <56> |
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": 7534,
"vin": [ {
"gen": {
"height": 7474
}
}
],
"vout": [ {
"amount": 34694647882353,
"target": {
"tagged_key": {
"key": "62572e2a11bcce71bf147c6210c5134826134bda0df618abfa3c0e705fa01cbe",
"view_tag": "56"
}
}
}
],
"extra": [ 1, 77, 52, 112, 210, 206, 247, 98, 181, 119, 185, 192, 59, 249, 86, 51, 179, 45, 211, 201, 90, 108, 101, 2, 47, 54, 76, 253, 104, 98, 183, 241, 211, 2, 9, 0, 0, 0, 2, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}