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: 32e2fce188099b33106a736643ab7592ddf3f44b9e82f5d1953f7375a6618c41
Tx prefix hash: 716050aaf5e2c0d68489659efc918bdaeb4d34875c0da4c220ab6cf94cd20f03
Tx public key: d5a990bdf41ca6840b4a11d94dbd2184e2539d5f2c5b42aa1b9b9a93cf3fc0c3
| Timestamp: 1780699319 | Timestamp [UTC]: 2026-06-05 22:41:59 | Age [y:d:h:m:s]: 00:003:02:53:58 |
| Block: 6031 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1855 | RingCT/type: yes/0 |
| Extra: 01d5a990bdf41ca6840b4a11d94dbd2184e2539d5f2c5b42aa1b9b9a93cf3fc0c3020900000002e49593ff00 | ||
1 output(s) for total of 34.782023459151 HMNY
| stealth address | amount | amount idx | tag |
| 00: 8ba2d8a8b46f0f4af13362559dd0f74a2ffebb10b0a4589715131f031d565894 | 34.782023459151 | 7500 of 0 | <4a> |
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": 6091,
"vin": [ {
"gen": {
"height": 6031
}
}
],
"vout": [ {
"amount": 34782023459151,
"target": {
"tagged_key": {
"key": "8ba2d8a8b46f0f4af13362559dd0f74a2ffebb10b0a4589715131f031d565894",
"view_tag": "4a"
}
}
}
],
"extra": [ 1, 213, 169, 144, 189, 244, 28, 166, 132, 11, 74, 17, 217, 77, 189, 33, 132, 226, 83, 157, 95, 44, 91, 66, 170, 27, 155, 154, 147, 207, 63, 192, 195, 2, 9, 0, 0, 0, 2, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}