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: 589025d7085086e2199097caf5962ac3940e5f04457642e1f381b0051c3f7947
Tx prefix hash: b5a9a2c7cc8d79d23fe956e6ac4c0e2d6ab61ee27cae4097177edd4a87426733
Tx public key: 0f2f4223c60f46297b5cf22f65b5a5de2eb7ace767b1c5400683d88f5eb966bb
| Timestamp: 1780997141 | Timestamp [UTC]: 2026-06-09 09:25:41 | Age [y:d:h:m:s]: 00:000:05:23:14 |
| Block: 8367 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 276 | RingCT/type: yes/0 |
| Extra: 010f2f4223c60f46297b5cf22f65b5a5de2eb7ace767b1c5400683d88f5eb966bb020900000001e49593ff00 | ||
1 output(s) for total of 34.627394432178 HMNY
| stealth address | amount | amount idx | tag |
| 00: bbd3342394b845b87916a5dba4c237b606af4786ce6a977fd0a6b7a6a235737e | 34.627394432178 | 10345 of 0 | <a2> |
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": 8427,
"vin": [ {
"gen": {
"height": 8367
}
}
],
"vout": [ {
"amount": 34627394432178,
"target": {
"tagged_key": {
"key": "bbd3342394b845b87916a5dba4c237b606af4786ce6a977fd0a6b7a6a235737e",
"view_tag": "a2"
}
}
}
],
"extra": [ 1, 15, 47, 66, 35, 198, 15, 70, 41, 123, 92, 242, 47, 101, 181, 165, 222, 46, 183, 172, 231, 103, 177, 197, 64, 6, 131, 216, 143, 94, 185, 102, 187, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}