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: 3dcf3acc7dd9708bbe4b7fb47fdb8d57a1a24fcc537b7e6012a549833bd5caf4
Tx prefix hash: 172c8b0ca5d1a5f1c4ba18e137d9b0eada65b93fe72e89b72e7a03d3be157db3
Tx public key: 34e31f2072dcc20c4fe31eaca285923818c95a34c1ab32d1dba7a3dff3fd30b9
| Timestamp: 1779995397 | Timestamp [UTC]: 2026-05-28 19:09:57 | Age [y:d:h:m:s]: 00:019:13:19:15 |
| Block: 4021 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 4724 | RingCT/type: yes/0 |
| Extra: 0134e31f2072dcc20c4fe31eaca285923818c95a34c1ab32d1dba7a3dff3fd30b902090000000426697be300 | ||
1 output(s) for total of 34.918245427584 HMNY
| stealth address | amount | amount idx | tag |
| 00: cc2d98329abbda84b98072692bd420f9ff5fdd0ff29649217d7e028a454493f3 | 34.918245427584 | 4974 of 0 | <46> |
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": 4081,
"vin": [ {
"gen": {
"height": 4021
}
}
],
"vout": [ {
"amount": 34918245427584,
"target": {
"tagged_key": {
"key": "cc2d98329abbda84b98072692bd420f9ff5fdd0ff29649217d7e028a454493f3",
"view_tag": "46"
}
}
}
],
"extra": [ 1, 52, 227, 31, 32, 114, 220, 194, 12, 79, 227, 30, 172, 162, 133, 146, 56, 24, 201, 90, 52, 193, 171, 50, 209, 219, 167, 163, 223, 243, 253, 48, 185, 2, 9, 0, 0, 0, 4, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}