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: 2a1b2c5de69b904706dcdce8511119deba4cf772aff6688a6e34bab3e481c23b
Tx prefix hash: e1b66bcda36d84258f99ea673e898279d4b33295e8138c9102a1a6e0308956ac
Tx public key: 3af4194207f8b59eae32ec22b0b524c8a53428ec8823836f968064c4bb879167
| Timestamp: 1780011551 | Timestamp [UTC]: 2026-05-28 23:39:11 | Age [y:d:h:m:s]: 00:011:03:01:25 |
| Block: 4098 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3798 | RingCT/type: yes/0 |
| Extra: 013af4194207f8b59eae32ec22b0b524c8a53428ec8823836f968064c4bb87916702090000000526697be300 | ||
1 output(s) for total of 34.913115486352 HMNY
| stealth address | amount | amount idx | tag |
| 00: 04ecb4bbd5c7f58391cac30b07b375d5da7e4c5b2c1ab2792adcddc6d2a6b61c | 34.913115486352 | 5101 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": 4158,
"vin": [ {
"gen": {
"height": 4098
}
}
],
"vout": [ {
"amount": 34913115486352,
"target": {
"tagged_key": {
"key": "04ecb4bbd5c7f58391cac30b07b375d5da7e4c5b2c1ab2792adcddc6d2a6b61c",
"view_tag": "da"
}
}
}
],
"extra": [ 1, 58, 244, 25, 66, 7, 248, 181, 158, 174, 50, 236, 34, 176, 181, 36, 200, 165, 52, 40, 236, 136, 35, 131, 111, 150, 128, 100, 196, 187, 135, 145, 103, 2, 9, 0, 0, 0, 5, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}