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: d99880b63fdff29e001420dae317ce2c159d9d43b5eca986bd2c64839327a0b9
Tx prefix hash: 056b7bf779ff48cab587d87c742a4916ece87392a0ec077d6665225712dc3e41
Tx public key: 5f66c41897f03a82b6918cf4bde416988c104e4ac2b073c3921b66ecff0e44fc
| Timestamp: 1780890626 | Timestamp [UTC]: 2026-06-08 03:50:26 | Age [y:d:h:m:s]: 00:000:23:48:24 |
| Block: 7720 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 222 | RingCT/type: yes/0 |
| Extra: 015f66c41897f03a82b6918cf4bde416988c104e4ac2b073c3921b66ecff0e44fc0209000000014a728a4c00 | ||
1 output(s) for total of 34.670152944886 HMNY
| stealth address | amount | amount idx | tag |
| 00: 3e02649a1be5df35556fa9e5dea84c92898e3bd8628243d883bbcae1cb678f9a | 34.670152944886 | 9556 of 0 | <7e> |
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": 7780,
"vin": [ {
"gen": {
"height": 7720
}
}
],
"vout": [ {
"amount": 34670152944886,
"target": {
"tagged_key": {
"key": "3e02649a1be5df35556fa9e5dea84c92898e3bd8628243d883bbcae1cb678f9a",
"view_tag": "7e"
}
}
}
],
"extra": [ 1, 95, 102, 196, 24, 151, 240, 58, 130, 182, 145, 140, 244, 189, 228, 22, 152, 140, 16, 78, 74, 194, 176, 115, 195, 146, 27, 102, 236, 255, 14, 68, 252, 2, 9, 0, 0, 0, 1, 74, 114, 138, 76, 0
],
"rct_signatures": {
"type": 0
}
}