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: 38fea19a3121541cfa532233e1a34a5c13e020325e50bbfa36d8e2fa957e5d27
Tx prefix hash: 4922773a71974772051410f441b8add57f3e08cd26495e46d33e78b88064d0fb
Tx public key: 2edd18abb34f8b5a1a37df90302104b45e705de936041305b743637e45b252df
| Timestamp: 1779852674 | Timestamp [UTC]: 2026-05-27 03:31:14 | Age [y:d:h:m:s]: 00:012:22:04:43 |
| Block: 2556 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 5330 | RingCT/type: yes/0 |
| Extra: 012edd18abb34f8b5a1a37df90302104b45e705de936041305b743637e45b252df02090000000126697be300 | ||
1 output(s) for total of 35.013325894451 HMNY
| stealth address | amount | amount idx | tag |
| 00: 018032b0ca1b9dd2be0a0c6bf211d94351ecc1bee22360ad2f47e65c8c4577bd | 35.013325894451 | 3010 of 0 | <d8> |
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": 2616,
"vin": [ {
"gen": {
"height": 2556
}
}
],
"vout": [ {
"amount": 35013325894451,
"target": {
"tagged_key": {
"key": "018032b0ca1b9dd2be0a0c6bf211d94351ecc1bee22360ad2f47e65c8c4577bd",
"view_tag": "d8"
}
}
}
],
"extra": [ 1, 46, 221, 24, 171, 179, 79, 139, 90, 26, 55, 223, 144, 48, 33, 4, 180, 94, 112, 93, 233, 54, 4, 19, 5, 183, 67, 99, 126, 69, 178, 82, 223, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}