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: 61842b153cc9523100121d627b48a7ac3067a194f80096f65a12d510409788e7
Tx prefix hash: a3ffa3c4ca621815794f8e370ea96285c4b3361a45d5adaf2b38e75937f32d05
Tx public key: 1ba324274514f1b14c6a20132d1d0ac921f67a07e85bee87aa7c30f664be3840
| Timestamp: 1779782792 | Timestamp [UTC]: 2026-05-26 08:06:32 | Age [y:d:h:m:s]: 00:013:18:43:16 |
| Block: 2131 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 5778 | RingCT/type: yes/0 |
| Extra: 011ba324274514f1b14c6a20132d1d0ac921f67a07e85bee87aa7c30f664be384002090000000226697be300 | ||
1 output(s) for total of 35.041720041644 HMNY
| stealth address | amount | amount idx | tag |
| 00: 3e62bd9e8e4543ca336c2ba16c99bb55eb9612a1959e27f3c378ff6b289b6267 | 35.041720041644 | 2455 of 0 | <8b> |
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": 2191,
"vin": [ {
"gen": {
"height": 2131
}
}
],
"vout": [ {
"amount": 35041720041644,
"target": {
"tagged_key": {
"key": "3e62bd9e8e4543ca336c2ba16c99bb55eb9612a1959e27f3c378ff6b289b6267",
"view_tag": "8b"
}
}
}
],
"extra": [ 1, 27, 163, 36, 39, 69, 20, 241, 177, 76, 106, 32, 19, 45, 29, 10, 201, 33, 246, 122, 7, 232, 91, 238, 135, 170, 124, 48, 246, 100, 190, 56, 64, 2, 9, 0, 0, 0, 2, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}