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: b94a1807e03540686c6c353f6c08af8f802f6df3dfbfd5ee075822037598c281
Tx prefix hash: 8cb5e1ae34f6bb51bc5a2b07421373d3bf8e90b57d49a16adf270e68566d8b83
Tx public key: 1724b2916c4b20b469f5b1ac16ca2bb2b66717769a6eb61a2211652dc03a6e3d
| Timestamp: 1780689449 | Timestamp [UTC]: 2026-06-05 19:57:29 | Age [y:d:h:m:s]: 00:003:05:38:28 |
| Block: 5596 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2290 | RingCT/type: yes/0 |
| Extra: 011724b2916c4b20b469f5b1ac16ca2bb2b66717769a6eb61a2211652dc03a6e3d020900000001e49593ff00 | ||
1 output(s) for total of 34.810893990448 HMNY
| stealth address | amount | amount idx | tag |
| 00: daa61bb04e56df5221f509eb29a4c5263b583f133d8d528f29fd4661f9ba9dfa | 34.810893990448 | 7041 of 0 | <29> |
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": 5656,
"vin": [ {
"gen": {
"height": 5596
}
}
],
"vout": [ {
"amount": 34810893990448,
"target": {
"tagged_key": {
"key": "daa61bb04e56df5221f509eb29a4c5263b583f133d8d528f29fd4661f9ba9dfa",
"view_tag": "29"
}
}
}
],
"extra": [ 1, 23, 36, 178, 145, 108, 75, 32, 180, 105, 245, 177, 172, 22, 202, 43, 178, 182, 103, 23, 118, 154, 110, 182, 26, 34, 17, 101, 45, 192, 58, 110, 61, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}