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: 27a65db0b9ea21535c706eb5786c6c156d2d1f7f43067fb6ff3fd056234980c8
Tx prefix hash: 948276d87b0ef8db8a4eda6f6ea8506b03f23fdad3cf1d0227e88809d9dea221
Tx public key: fe90d195f788f4db9adbbbe47d968373cd0a4bcc5fc9c156683efc97509d1da6
| Timestamp: 1780069365 | Timestamp [UTC]: 2026-05-29 15:42:45 | Age [y:d:h:m:s]: 00:010:09:53:12 |
| Block: 4626 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3260 | RingCT/type: yes/0 |
| Extra: 01fe90d195f788f4db9adbbbe47d968373cd0a4bcc5fc9c156683efc97509d1da602090000000626697be300 | ||
1 output(s) for total of 34.875358282867 HMNY
| stealth address | amount | amount idx | tag |
| 00: d6a8164a3adf74d86203847ae801335542eab94f13b1f2abede78e9a3a6c6c1b | 34.875358282867 | 5809 of 0 | <83> |
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": 4686,
"vin": [ {
"gen": {
"height": 4626
}
}
],
"vout": [ {
"amount": 34875358282867,
"target": {
"tagged_key": {
"key": "d6a8164a3adf74d86203847ae801335542eab94f13b1f2abede78e9a3a6c6c1b",
"view_tag": "83"
}
}
}
],
"extra": [ 1, 254, 144, 209, 149, 247, 136, 244, 219, 154, 219, 187, 228, 125, 150, 131, 115, 205, 10, 75, 204, 95, 201, 193, 86, 104, 62, 252, 151, 80, 157, 29, 166, 2, 9, 0, 0, 0, 6, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}