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: 5519ba7b1ca4c2c432115429671a21bfec7bddad265d89db40fe7da5e7405984
Tx prefix hash: aa0aa79cc0906938251a9e6fa96f254b6e7bcd51a3a58e7a84127fe4c3e45167
Tx public key: 7152e63c3ebfe5db4e76299bb4541487041e7c71fd2461115afacdc2d26ce39d
| Timestamp: 1779804761 | Timestamp [UTC]: 2026-05-26 14:12:41 | Age [y:d:h:m:s]: 00:013:12:37:07 |
| Block: 2340 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 5580 | RingCT/type: yes/0 |
| Extra: 017152e63c3ebfe5db4e76299bb4541487041e7c71fd2461115afacdc2d26ce39d02090000000326697be300 | ||
1 output(s) for total of 35.027753925853 HMNY
| stealth address | amount | amount idx | tag |
| 00: aaa408b0e3dd8d1ea04dda3872c57fdb522545a8eb5a17ce7526305baac69c6f | 35.027753925853 | 2738 of 0 | <a4> |
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": 2400,
"vin": [ {
"gen": {
"height": 2340
}
}
],
"vout": [ {
"amount": 35027753925853,
"target": {
"tagged_key": {
"key": "aaa408b0e3dd8d1ea04dda3872c57fdb522545a8eb5a17ce7526305baac69c6f",
"view_tag": "a4"
}
}
}
],
"extra": [ 1, 113, 82, 230, 60, 62, 191, 229, 219, 78, 118, 41, 155, 180, 84, 20, 135, 4, 30, 124, 113, 253, 36, 97, 17, 90, 250, 205, 194, 210, 108, 227, 157, 2, 9, 0, 0, 0, 3, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}