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: 6e7c0e6eccdbdb37605f3861544a3187b3a646c0b54f925e26ea9c78301e8486
Tx prefix hash: e9eeaac87ea595db65f5dbb12fcdd55348a0b65a9ae71197137c4e2e08bb3b0a
Tx public key: 6950150caaaa89f9216e63c727b3433137e6e70331598b6ca9cdd7469804ace2
| Timestamp: 1779450631 | Timestamp [UTC]: 2026-05-22 11:50:31 | Age [y:d:h:m:s]: 00:017:13:45:26 |
| Block: 323 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 7563 | RingCT/type: yes/0 |
| Extra: 016950150caaaa89f9216e63c727b3433137e6e70331598b6ca9cdd7469804ace20209000000064438f87f00 | ||
1 output(s) for total of 35.162769648560 HMNY
| stealth address | amount | amount idx | tag |
| 00: 2726fec471a274ddedc40c4380e0b2f0deb3018e41d74db136401846cc1fb224 | 35.162769648560 | 319 of 0 | <99> |
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": 383,
"vin": [ {
"gen": {
"height": 323
}
}
],
"vout": [ {
"amount": 35162769648560,
"target": {
"tagged_key": {
"key": "2726fec471a274ddedc40c4380e0b2f0deb3018e41d74db136401846cc1fb224",
"view_tag": "99"
}
}
}
],
"extra": [ 1, 105, 80, 21, 12, 170, 170, 137, 249, 33, 110, 99, 199, 39, 179, 67, 49, 55, 230, 231, 3, 49, 89, 139, 108, 169, 205, 215, 70, 152, 4, 172, 226, 2, 9, 0, 0, 0, 6, 68, 56, 248, 127, 0
],
"rct_signatures": {
"type": 0
}
}