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: a71a47401daf1cabd1e130113b4173d315d4cb0f160d785b81ff2121c867538d
Tx prefix hash: 8220305cd3b4c998e7d386182e91f6d4e3d2a1372e7955b8a587f67c4365f3df
Tx public key: 25ecf4df6d0cc3df1dfd92f8a8d1a31f82782d74e6773c4f623d65b0aa89ce24
| Timestamp: 1780054059 | Timestamp [UTC]: 2026-05-29 11:27:39 | Age [y:d:h:m:s]: 00:010:14:08:18 |
| Block: 4426 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3460 | RingCT/type: yes/0 |
| Extra: 0125ecf4df6d0cc3df1dfd92f8a8d1a31f82782d74e6773c4f623d65b0aa89ce2402090000000526697be300 | ||
1 output(s) for total of 34.888664726786 HMNY
| stealth address | amount | amount idx | tag |
| 00: c610cf2ab1061f0b9aa1a2d29931d53b289d134013a9f1cf62de627035b7a515 | 34.888664726786 | 5540 of 0 | <73> |
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": 4486,
"vin": [ {
"gen": {
"height": 4426
}
}
],
"vout": [ {
"amount": 34888664726786,
"target": {
"tagged_key": {
"key": "c610cf2ab1061f0b9aa1a2d29931d53b289d134013a9f1cf62de627035b7a515",
"view_tag": "73"
}
}
}
],
"extra": [ 1, 37, 236, 244, 223, 109, 12, 195, 223, 29, 253, 146, 248, 168, 209, 163, 31, 130, 120, 45, 116, 230, 119, 60, 79, 98, 61, 101, 176, 170, 137, 206, 36, 2, 9, 0, 0, 0, 5, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}