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: 9c892425936c3a274ee65f2d269c429772d4ee22876b7be3d20120e3c74291f1
Tx prefix hash: 3a00fbac20a5a6728f4a3dc0e19ea0b81e2df4e75859335f6605f05687574c8b
Tx public key: c1cec773f9cc9ec7b8e2c738cfbb0c4d56a77cb149ba1a4d32fb69fe4e73ed9f
| Timestamp: 1781007529 | Timestamp [UTC]: 2026-06-09 12:18:49 | Age [y:d:h:m:s]: 00:003:22:43:27 |
| Block: 8567 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 178 | RingCT/type: yes/0 |
| Extra: 01c1cec773f9cc9ec7b8e2c738cfbb0c4d56a77cb149ba1a4d32fb69fe4e73ed9f020900000003e49593ff00 | ||
1 output(s) for total of 34.614187636054 HMNY
| stealth address | amount | amount idx | tag |
| 00: 578e948d50a200ffa82ca52f4f015d0926ccfb540497f774cbdeece55682bf61 | 34.614187636054 | 10579 of 0 | <2d> |
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": 8627,
"vin": [ {
"gen": {
"height": 8567
}
}
],
"vout": [ {
"amount": 34614187636054,
"target": {
"tagged_key": {
"key": "578e948d50a200ffa82ca52f4f015d0926ccfb540497f774cbdeece55682bf61",
"view_tag": "2d"
}
}
}
],
"extra": [ 1, 193, 206, 199, 115, 249, 204, 158, 199, 184, 226, 199, 56, 207, 187, 12, 77, 86, 167, 124, 177, 73, 186, 26, 77, 50, 251, 105, 254, 78, 115, 237, 159, 2, 9, 0, 0, 0, 3, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}