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: d72d55f3ac787a82a528200e3d6141af7e490affe792b1dd90fdd2c0a50887fb
Tx prefix hash: fe8fe4deb4ae86c637d6f98d0c43230a4999df70661ae8ea2f6e926c9d2345c1
Tx public key: a48b0305e4d3a55f9043f13331e0f4578a0c4b927fd3bd232cf4e2125b7df91b
| Timestamp: 1779641125 | Timestamp [UTC]: 2026-05-24 16:45:25 | Age [y:d:h:m:s]: 00:015:08:50:32 |
| Block: 1323 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 6563 | RingCT/type: yes/0 |
| Extra: 01a48b0305e4d3a55f9043f13331e0f4578a0c4b927fd3bd232cf4e2125b7df91b020900000001ba6d17be00 | ||
1 output(s) for total of 35.095765844165 HMNY
| stealth address | amount | amount idx | tag |
| 00: 61818ec17c5fb7a6858b5279e29485e26e2161de7e6d915f40c68998d0591c94 | 35.095765844165 | 1471 of 0 | <d2> |
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": 1383,
"vin": [ {
"gen": {
"height": 1323
}
}
],
"vout": [ {
"amount": 35095765844165,
"target": {
"tagged_key": {
"key": "61818ec17c5fb7a6858b5279e29485e26e2161de7e6d915f40c68998d0591c94",
"view_tag": "d2"
}
}
}
],
"extra": [ 1, 164, 139, 3, 5, 228, 211, 165, 95, 144, 67, 241, 51, 49, 224, 244, 87, 138, 12, 75, 146, 127, 211, 189, 35, 44, 244, 226, 18, 91, 125, 249, 27, 2, 9, 0, 0, 0, 1, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}