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: 4a6dbddfbf6364f9aed605f0fb9fe837a295634922f6e58ec126c6a1e39ada19
Tx prefix hash: e14149bf972d6b8994b90da1b76cfb0478e63a2f269565bef08bb30ebad1a0bf
Tx public key: eeaa7651e84b4ac72c1bd6c3260a3e37a6f62bb6d4f8eaef24c8f16ee0f59bd2
| Timestamp: 1780734437 | Timestamp [UTC]: 2026-06-06 08:27:17 | Age [y:d:h:m:s]: 00:002:17:08:40 |
| Block: 6350 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1536 | RingCT/type: yes/0 |
| Extra: 01eeaa7651e84b4ac72c1bd6c3260a3e37a6f62bb6d4f8eaef24c8f16ee0f59bd2020900000002e49593ff00 | ||
1 output(s) for total of 34.760866954984 HMNY
| stealth address | amount | amount idx | tag |
| 00: aebbf3e37455db9b641f8bcfb2c0134b88c88e3a62e83a1ebed5d401eb0e8942 | 34.760866954984 | 7837 of 0 | <11> |
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": 6410,
"vin": [ {
"gen": {
"height": 6350
}
}
],
"vout": [ {
"amount": 34760866954984,
"target": {
"tagged_key": {
"key": "aebbf3e37455db9b641f8bcfb2c0134b88c88e3a62e83a1ebed5d401eb0e8942",
"view_tag": "11"
}
}
}
],
"extra": [ 1, 238, 170, 118, 81, 232, 75, 74, 199, 44, 27, 214, 195, 38, 10, 62, 55, 166, 246, 43, 182, 212, 248, 234, 239, 36, 200, 241, 110, 224, 245, 155, 210, 2, 9, 0, 0, 0, 2, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}