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: d94b3a4e4ba6c78060a3b7426db3182da6dce812b66eb12f5120a32eb3f8232a
Tx prefix hash: c367ae5c91d9afd988c9dede5c1b214caa3a7f670589e9ee1bb203dd83fc760b
Tx public key: 5d93dc607d8d78823d6d703c6b1ec0734d18be106d0efb5c3d77c48c31e5260b
| Timestamp: 1779987455 | Timestamp [UTC]: 2026-05-28 16:57:35 | Age [y:d:h:m:s]: 00:011:08:38:22 |
| Block: 3970 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3916 | RingCT/type: yes/0 |
| Extra: 015d93dc607d8d78823d6d703c6b1ec0734d18be106d0efb5c3d77c48c31e5260b02090000000626697be300 | ||
1 output(s) for total of 34.919022405852 HMNY
| stealth address | amount | amount idx | tag |
| 00: f1c9d67e3136327f552ac1aa89278354b90fa71f162fbfdd9a8461c00043eaf2 | 34.919022405852 | 4895 of 0 | <da> |
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": 4030,
"vin": [ {
"gen": {
"height": 3970
}
}
],
"vout": [ {
"amount": 34919022405852,
"target": {
"tagged_key": {
"key": "f1c9d67e3136327f552ac1aa89278354b90fa71f162fbfdd9a8461c00043eaf2",
"view_tag": "da"
}
}
}
],
"extra": [ 1, 93, 147, 220, 96, 125, 141, 120, 130, 61, 109, 112, 60, 107, 30, 192, 115, 77, 24, 190, 16, 109, 14, 251, 92, 61, 119, 196, 140, 49, 229, 38, 11, 2, 9, 0, 0, 0, 6, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}