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: cad96af4221c40f23a48d9bb9865483526d64ea2ab609a818054d5c57fd8c31b
Tx prefix hash: 0cc7481678640299d5729fd4e94399b140a8384fd84c6a77e43e628d0951bef6
Tx public key: fcfc23391b2f9818a9dd6bf25317acd7dd7610a7db7cb5dd3c020022390d2e57
| Timestamp: 1780395233 | Timestamp [UTC]: 2026-06-02 10:13:53 | Age [y:d:h:m:s]: 00:006:15:22:04 |
| Block: 5242 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2644 | RingCT/type: yes/0 |
| Extra: 01fcfc23391b2f9818a9dd6bf25317acd7dd7610a7db7cb5dd3c020022390d2e5702090000000126697be300 | ||
1 output(s) for total of 34.839425914670 HMNY
| stealth address | amount | amount idx | tag |
| 00: 7f8fa58f279e3298742d0bab962fa6ab78201c67f14837783c3f12d0090faa8a | 34.839425914670 | 6635 of 0 | <72> |
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": 5302,
"vin": [ {
"gen": {
"height": 5242
}
}
],
"vout": [ {
"amount": 34839425914670,
"target": {
"tagged_key": {
"key": "7f8fa58f279e3298742d0bab962fa6ab78201c67f14837783c3f12d0090faa8a",
"view_tag": "72"
}
}
}
],
"extra": [ 1, 252, 252, 35, 57, 27, 47, 152, 24, 169, 221, 107, 242, 83, 23, 172, 215, 221, 118, 16, 167, 219, 124, 181, 221, 60, 2, 0, 34, 57, 13, 46, 87, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}