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: 277a536814776927bb171c6d4d131d732cb6c6395b5bc9cbda793fcff5f3ea6c
Tx prefix hash: e739483010325c08ebea9a4f6a0f37a18a1e19891d4e0b52600ea8dc8c149706
Tx public key: 80b97044ae6bad9eb03e3fc5c0a7267f638260fdeb199706e8faa7d8d34d1c2c
| Timestamp: 1780804613 | Timestamp [UTC]: 2026-06-07 03:56:53 | Age [y:d:h:m:s]: 00:001:21:39:04 |
| Block: 6912 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 974 | RingCT/type: yes/0 |
| Extra: 0180b97044ae6bad9eb03e3fc5c0a7267f638260fdeb199706e8faa7d8d34d1c2c020900000001e49593ff00 | ||
1 output(s) for total of 34.723625669319 HMNY
| stealth address | amount | amount idx | tag |
| 00: bc02f23436987afa6f97b578c43a0c612b613a8a436dbbd210daa84a8dea41fa | 34.723625669319 | 8528 of 0 | <d4> |
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": 6972,
"vin": [ {
"gen": {
"height": 6912
}
}
],
"vout": [ {
"amount": 34723625669319,
"target": {
"tagged_key": {
"key": "bc02f23436987afa6f97b578c43a0c612b613a8a436dbbd210daa84a8dea41fa",
"view_tag": "d4"
}
}
}
],
"extra": [ 1, 128, 185, 112, 68, 174, 107, 173, 158, 176, 62, 63, 197, 192, 167, 38, 127, 99, 130, 96, 253, 235, 25, 151, 6, 232, 250, 167, 216, 211, 77, 28, 44, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}