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: d363574a2655bdae681229be49c1af4ecf2ddc0ae353fe769e2ae1d8c597f6fc
Tx prefix hash: 196b692316cc7e5c7e23859f5b7a41e4dee0591245d8c9da36ccf1107d02bcb5
Tx public key: c28ab0fbe961f76363428c447e0dfde1aa569d11a633da0c331f2a4398c1a452
| Timestamp: 1780809066 | Timestamp [UTC]: 2026-06-07 05:11:06 | Age [y:d:h:m:s]: 00:010:03:25:08 |
| Block: 6994 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1751 | RingCT/type: yes/0 |
| Extra: 01c28ab0fbe961f76363428c447e0dfde1aa569d11a633da0c331f2a4398c1a452020900000001e49593ff00 | ||
1 output(s) for total of 34.718195223904 HMNY
| stealth address | amount | amount idx | tag |
| 00: 235f1447fa8fee23fa228f944716434d64d3a02edc312fc8d33a31866281d24d | 34.718195223904 | 8626 of 0 | <78> |
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": 7054,
"vin": [ {
"gen": {
"height": 6994
}
}
],
"vout": [ {
"amount": 34718195223904,
"target": {
"tagged_key": {
"key": "235f1447fa8fee23fa228f944716434d64d3a02edc312fc8d33a31866281d24d",
"view_tag": "78"
}
}
}
],
"extra": [ 1, 194, 138, 176, 251, 233, 97, 247, 99, 99, 66, 140, 68, 126, 13, 253, 225, 170, 86, 157, 17, 166, 51, 218, 12, 51, 31, 42, 67, 152, 193, 164, 82, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}