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: 30e3b7827ac6170800d3fb1d172df922fa3801272c99c579acef25626d1508aa
Tx prefix hash: 3f1e39518b3d6d49e5d54abd3abe349a947a281ce83c2516c524df8ed9984bb3
Tx public key: 27d1a7c6e16dc5046f83ddc38bcddc08935116a8d8f694346d4f2b8db1fc4b0a
| Timestamp: 1779714311 | Timestamp [UTC]: 2026-05-25 13:05:11 | Age [y:d:h:m:s]: 00:014:10:13:42 |
| Block: 1615 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 6271 | RingCT/type: yes/0 |
| Extra: 0127d1a7c6e16dc5046f83ddc38bcddc08935116a8d8f694346d4f2b8db1fc4b0a020900000003ba6d17be00 | ||
1 output(s) for total of 35.076224828266 HMNY
| stealth address | amount | amount idx | tag |
| 00: 00741124e75bd706656d8dffd5c42048f82653fb61b71d0b1eaeb926948c3c05 | 35.076224828266 | 1773 of 0 | <07> |
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": 1675,
"vin": [ {
"gen": {
"height": 1615
}
}
],
"vout": [ {
"amount": 35076224828266,
"target": {
"tagged_key": {
"key": "00741124e75bd706656d8dffd5c42048f82653fb61b71d0b1eaeb926948c3c05",
"view_tag": "07"
}
}
}
],
"extra": [ 1, 39, 209, 167, 198, 225, 109, 197, 4, 111, 131, 221, 195, 139, 205, 220, 8, 147, 81, 22, 168, 216, 246, 148, 52, 109, 79, 43, 141, 177, 252, 75, 10, 2, 9, 0, 0, 0, 3, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}