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: 86ecf1e3228be6026f8256863a729e2582fc766e895dbf6e275e4b4059f328ad
Tx prefix hash: d02852098e2b23f27229890e2cc2015e2ae5df5732dd3a6a27ee2b3d4b3df12d
Tx public key: 8acbc22369eada2527e62b2b4738a3592c0a172e68738afcd1bbc0d7645dfc55
| Timestamp: 1780988617 | Timestamp [UTC]: 2026-06-09 07:03:37 | Age [y:d:h:m:s]: 00:000:08:56:07 |
| Block: 8186 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 505 | RingCT/type: yes/0 |
| Extra: 018acbc22369eada2527e62b2b4738a3592c0a172e68738afcd1bbc0d7645dfc55020900000001e49593ff00 | ||
1 output(s) for total of 34.639350926263 HMNY
| stealth address | amount | amount idx | tag |
| 00: 3f544268e9bcf88ef18cecc74c3b9d06d15dab773db73a58223f61c4fa1424f9 | 34.639350926263 | 10136 of 0 | <ae> |
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": 8246,
"vin": [ {
"gen": {
"height": 8186
}
}
],
"vout": [ {
"amount": 34639350926263,
"target": {
"tagged_key": {
"key": "3f544268e9bcf88ef18cecc74c3b9d06d15dab773db73a58223f61c4fa1424f9",
"view_tag": "ae"
}
}
}
],
"extra": [ 1, 138, 203, 194, 35, 105, 234, 218, 37, 39, 230, 43, 43, 71, 56, 163, 89, 44, 10, 23, 46, 104, 115, 138, 252, 209, 187, 192, 215, 100, 93, 252, 85, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}