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: f67cfaf94f48087d80cc0b9f76260282fa57ef6a2f38b53a857963bbe152b1e1
Tx prefix hash: ea4bd4df4156c0e4539f7d36d64d05c50abd676ded5b300ef30e98b03d286f6f
Tx public key: f1e9931a9d0e56798207a1683c8d7f494d21f65c49d179610272291dbd71d92b
| Timestamp: 1781005977 | Timestamp [UTC]: 2026-06-09 11:52:57 | Age [y:d:h:m:s]: 00:006:02:59:55 |
| Block: 8545 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 200 | RingCT/type: yes/0 |
| Extra: 01f1e9931a9d0e56798207a1683c8d7f494d21f65c49d179610272291dbd71d92b020900000001e49593ff00 | ||
1 output(s) for total of 34.615640137030 HMNY
| stealth address | amount | amount idx | tag |
| 00: a950d85945957f13a313c37710c1fbe8591b67fce8fa290f862b3691aa019965 | 34.615640137030 | 10553 of 0 | <56> |
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": 8605,
"vin": [ {
"gen": {
"height": 8545
}
}
],
"vout": [ {
"amount": 34615640137030,
"target": {
"tagged_key": {
"key": "a950d85945957f13a313c37710c1fbe8591b67fce8fa290f862b3691aa019965",
"view_tag": "56"
}
}
}
],
"extra": [ 1, 241, 233, 147, 26, 157, 14, 86, 121, 130, 7, 161, 104, 60, 141, 127, 73, 77, 33, 246, 92, 73, 209, 121, 97, 2, 114, 41, 29, 189, 113, 217, 43, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}