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: 24144f850ae49df78491772fcd52a1be5f285761e580015487bb3d17d5a1a04b
Tx prefix hash: 7ca028f255db033e6b93734981f8d0e626f0b704df98ea31da801deddbc7042e
Tx public key: bc43c90f26c1d2f892eec6fbcaa6a9b5c52c43d02a0c1790626ae092525e6a8c
| Timestamp: 1780041105 | Timestamp [UTC]: 2026-05-29 07:51:45 | Age [y:d:h:m:s]: 00:010:16:55:02 |
| Block: 4290 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3596 | RingCT/type: yes/0 |
| Extra: 01bc43c90f26c1d2f892eec6fbcaa6a9b5c52c43d02a0c1790626ae092525e6a8c02090000000126697be300 | ||
1 output(s) for total of 34.897716008504 HMNY
| stealth address | amount | amount idx | tag |
| 00: b8e25e415007e11e370ca7c20961c943aa0f8d4804caee0a34d18f46a1a6d0f4 | 34.897716008504 | 5360 of 0 | <a0> |
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": 4350,
"vin": [ {
"gen": {
"height": 4290
}
}
],
"vout": [ {
"amount": 34897716008504,
"target": {
"tagged_key": {
"key": "b8e25e415007e11e370ca7c20961c943aa0f8d4804caee0a34d18f46a1a6d0f4",
"view_tag": "a0"
}
}
}
],
"extra": [ 1, 188, 67, 201, 15, 38, 193, 210, 248, 146, 238, 198, 251, 202, 166, 169, 181, 197, 44, 67, 208, 42, 12, 23, 144, 98, 106, 224, 146, 82, 94, 106, 140, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}