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: 00d685da36a95fe01bcbfd9f0843b87d527dd60a7f9bcb0d4416df2847775a5f
Tx prefix hash: 440c0e70fa64fd52f17b077310975cb27aa8a14b07b3f9e60d1e35a0b8d5a2f6
Tx public key: f51dc0cd8fcf7d68267956fe19523d71ab25c96b85f553ec1e1fc2ff4343ebea
| Timestamp: 1779629983 | Timestamp [UTC]: 2026-05-24 13:39:43 | Age [y:d:h:m:s]: 00:015:13:00:53 |
| Block: 854 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 7042 | RingCT/type: yes/0 |
| Extra: 01f51dc0cd8fcf7d68267956fe19523d71ab25c96b85f553ec1e1fc2ff4343ebea020900000002ba6d17be00 | ||
1 output(s) for total of 35.127174715182 HMNY
| stealth address | amount | amount idx | tag |
| 00: 8db37bf35e5d2fa81fd91980aadef51d3aae66c83f09cf942a2f91ae97a9caf6 | 35.127174715182 | 986 of 0 | <bf> |
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": 914,
"vin": [ {
"gen": {
"height": 854
}
}
],
"vout": [ {
"amount": 35127174715182,
"target": {
"tagged_key": {
"key": "8db37bf35e5d2fa81fd91980aadef51d3aae66c83f09cf942a2f91ae97a9caf6",
"view_tag": "bf"
}
}
}
],
"extra": [ 1, 245, 29, 192, 205, 143, 207, 125, 104, 38, 121, 86, 254, 25, 82, 61, 113, 171, 37, 201, 107, 133, 245, 83, 236, 30, 31, 194, 255, 67, 67, 235, 234, 2, 9, 0, 0, 0, 2, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}