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: 3400ba25fcb2ab563e49dbcd1da448089a0b003f1095cf8d0d818e1466c6fee7
Tx prefix hash: e3b2978d72e1aed0b099277d077a60ee6d90bfc33e08f80fd67f90c8e9e515c6
Tx public key: b92ac1b5142dd2f1b4ad5115abb7f48d4b7c6d85f2104007eab17e468b5c6f5d
| Timestamp: 1780708193 | Timestamp [UTC]: 2026-06-06 01:09:53 | Age [y:d:h:m:s]: 00:007:09:52:23 |
| Block: 6136 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2609 | RingCT/type: yes/0 |
| Extra: 01b92ac1b5142dd2f1b4ad5115abb7f48d4b7c6d85f2104007eab17e468b5c6f5d020900000001e49593ff00 | ||
1 output(s) for total of 34.775058298281 HMNY
| stealth address | amount | amount idx | tag |
| 00: a22bb208c9de8b5b1508b1c0f30c4b43da8e338dd1c6b8c69e1a11532e039280 | 34.775058298281 | 7611 of 0 | <83> |
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": 6196,
"vin": [ {
"gen": {
"height": 6136
}
}
],
"vout": [ {
"amount": 34775058298281,
"target": {
"tagged_key": {
"key": "a22bb208c9de8b5b1508b1c0f30c4b43da8e338dd1c6b8c69e1a11532e039280",
"view_tag": "83"
}
}
}
],
"extra": [ 1, 185, 42, 193, 181, 20, 45, 210, 241, 180, 173, 81, 21, 171, 183, 244, 141, 75, 124, 109, 133, 242, 16, 64, 7, 234, 177, 126, 70, 139, 92, 111, 93, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}