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: ba7cf1b3bd42a89ef1d2c7cd827479b0fe9f40175d3e13c128199ff8998e03cd
Tx prefix hash: 2f03969f876652b6007ffa014f2836d5ff17d6627120f6df88fda13d2cb27940
Tx public key: 0239b1b04abfad3f0c96e5e1eb31f29c1f5934f20e8653e78bbff2fe9336c4e6
| Timestamp: 1780782422 | Timestamp [UTC]: 2026-06-06 21:47:02 | Age [y:d:h:m:s]: 00:002:02:59:45 |
| Block: 6775 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1111 | RingCT/type: yes/0 |
| Extra: 010239b1b04abfad3f0c96e5e1eb31f29c1f5934f20e8653e78bbff2fe9336c4e6020900000001e49593ff00 | ||
1 output(s) for total of 34.732700381776 HMNY
| stealth address | amount | amount idx | tag |
| 00: 53bb486048a55f4f76b9f1e7f6426728e50b2026a9287bbcae37d855c54a7b6e | 34.732700381776 | 8365 of 0 | <52> |
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": 6835,
"vin": [ {
"gen": {
"height": 6775
}
}
],
"vout": [ {
"amount": 34732700381776,
"target": {
"tagged_key": {
"key": "53bb486048a55f4f76b9f1e7f6426728e50b2026a9287bbcae37d855c54a7b6e",
"view_tag": "52"
}
}
}
],
"extra": [ 1, 2, 57, 177, 176, 74, 191, 173, 63, 12, 150, 229, 225, 235, 49, 242, 156, 31, 89, 52, 242, 14, 134, 83, 231, 139, 191, 242, 254, 147, 54, 196, 230, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}