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: 3bce9feaad743cb3eb22fab3754ae5e18f7aaad2ee008db8b1cd0de7640769af
Tx prefix hash: d01f86523fadfeb8d4f96bf46fba2a140f0ae37dde6c6988fd1e5ee533dfb9a3
Tx public key: 86d2fd44f0e3338e8c897481c40760be57c7311c4e037fd1eb502fd8407449a6
| Timestamp: 1780808928 | Timestamp [UTC]: 2026-06-07 05:08:48 | Age [y:d:h:m:s]: 00:008:03:10:47 |
| Block: 6991 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1754 | RingCT/type: yes/0 |
| Extra: 0186d2fd44f0e3338e8c897481c40760be57c7311c4e037fd1eb502fd8407449a6020900000001e49593ff00 | ||
1 output(s) for total of 34.718393883768 HMNY
| stealth address | amount | amount idx | tag |
| 00: 7bebe970c58096f82bcd007a8fcac52dd0b133cf1818157586fe78fda648d254 | 34.718393883768 | 8621 of 0 | <66> |
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": 7051,
"vin": [ {
"gen": {
"height": 6991
}
}
],
"vout": [ {
"amount": 34718393883768,
"target": {
"tagged_key": {
"key": "7bebe970c58096f82bcd007a8fcac52dd0b133cf1818157586fe78fda648d254",
"view_tag": "66"
}
}
}
],
"extra": [ 1, 134, 210, 253, 68, 240, 227, 51, 142, 140, 137, 116, 129, 196, 7, 96, 190, 87, 199, 49, 28, 78, 3, 127, 209, 235, 80, 47, 216, 64, 116, 73, 166, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}