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: 70d5d7cf248cc797aec552b4c0aa18e2d813f7e642d2d869b3cf8b1e39f04317
Tx prefix hash: 3b37d1553454130952bc7f35d084a5e64d3a8700e4a95b378cd4471fc87b6a33
Tx public key: 15f9412c9b01df5bcc9ddee3bb6dfaf2b3a559df557a240a1fea19f15c6001f7
| Timestamp: 1779860302 | Timestamp [UTC]: 2026-05-27 05:38:22 | Age [y:d:h:m:s]: 00:017:05:23:54 |
| Block: 2674 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 6071 | RingCT/type: yes/0 |
| Extra: 0115f9412c9b01df5bcc9ddee3bb6dfaf2b3a559df557a240a1fea19f15c6001f702090000000326697be300 | ||
1 output(s) for total of 35.014446424600 HMNY
| stealth address | amount | amount idx | tag |
| 00: 0483e15b4d7757ac177f31d9717b3e99237b0d67027196afb13b57180bafb49f | 35.014446424600 | 3152 of 0 | <ff> |
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": 2734,
"vin": [ {
"gen": {
"height": 2674
}
}
],
"vout": [ {
"amount": 35014446424600,
"target": {
"tagged_key": {
"key": "0483e15b4d7757ac177f31d9717b3e99237b0d67027196afb13b57180bafb49f",
"view_tag": "ff"
}
}
}
],
"extra": [ 1, 21, 249, 65, 44, 155, 1, 223, 91, 204, 157, 222, 227, 187, 109, 250, 242, 179, 165, 89, 223, 85, 122, 36, 10, 31, 234, 25, 241, 92, 96, 1, 247, 2, 9, 0, 0, 0, 3, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}