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: 310b43105316279a136d5642b3ed3d35ec05a607ebe89c7f8283f2e31b7aa39b
Tx prefix hash: 03c9877b633f246076c8e6f130429593788c7b28b16fd05bf200978a0e78facb
Tx public key: 05dddcc67b8e33503c1d32df6f7141ce35fc9fc7a1f340de67fb7ba17a04435e
| Timestamp: 1779969441 | Timestamp [UTC]: 2026-05-28 11:57:21 | Age [y:d:h:m:s]: 00:015:23:04:55 |
| Block: 3837 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 4908 | RingCT/type: yes/0 |
| Extra: 0105dddcc67b8e33503c1d32df6f7141ce35fc9fc7a1f340de67fb7ba17a04435e02090000000a26697be300 | ||
1 output(s) for total of 34.927881703657 HMNY
| stealth address | amount | amount idx | tag |
| 00: 8b8ac65327fd35d029c6fc75826b061049bca231437cd23dc5cf03f54eedf30a | 34.927881703657 | 4677 of 0 | <0b> |
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": 3897,
"vin": [ {
"gen": {
"height": 3837
}
}
],
"vout": [ {
"amount": 34927881703657,
"target": {
"tagged_key": {
"key": "8b8ac65327fd35d029c6fc75826b061049bca231437cd23dc5cf03f54eedf30a",
"view_tag": "0b"
}
}
}
],
"extra": [ 1, 5, 221, 220, 198, 123, 142, 51, 80, 60, 29, 50, 223, 111, 113, 65, 206, 53, 252, 159, 199, 161, 243, 64, 222, 103, 251, 123, 161, 122, 4, 67, 94, 2, 9, 0, 0, 0, 10, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}