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: 893eca99fac162b68d6302887ed1d007e44720ce779dd40670a55d68c8b2ba74
Tx prefix hash: edaedee259ef1904d5278784593f22d67de96fe6d7b1e7f2af7984f6f4db1707
Tx public key: 66e45ab50e3abcd4e37083cdec1f11a6673b11f37e2aa993d9619f7e9180279c
| Timestamp: 1780691898 | Timestamp [UTC]: 2026-06-05 20:38:18 | Age [y:d:h:m:s]: 00:011:11:27:03 |
| Block: 5759 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2986 | RingCT/type: yes/0 |
| Extra: 0166e45ab50e3abcd4e37083cdec1f11a6673b11f37e2aa993d9619f7e9180279c020900000001e49593ff00 | ||
1 output(s) for total of 34.800073031019 HMNY
| stealth address | amount | amount idx | tag |
| 00: c202e0fb817f551fa2226fbc863c00725c92cc54ffa19e2f0a2adef081cc43ae | 34.800073031019 | 7212 of 0 | <b2> |
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": 5819,
"vin": [ {
"gen": {
"height": 5759
}
}
],
"vout": [ {
"amount": 34800073031019,
"target": {
"tagged_key": {
"key": "c202e0fb817f551fa2226fbc863c00725c92cc54ffa19e2f0a2adef081cc43ae",
"view_tag": "b2"
}
}
}
],
"extra": [ 1, 102, 228, 90, 181, 14, 58, 188, 212, 227, 112, 131, 205, 236, 31, 17, 166, 103, 59, 17, 243, 126, 42, 169, 147, 217, 97, 159, 126, 145, 128, 39, 156, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}