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: 75c1ff7f98f1057c557dde7f14ae29f102bc5ca0e9d586ac81f476afac48fa2b
Tx prefix hash: 599b17b891dabc4ff923eec6ac1b82dc696137fdaf0d9433da77c91f07e2c3e9
Tx public key: cfeb4328bdf3c711f0fd2ce171ccf704e62a32dee70ac0c2ef725c1b5fbbf2a3
| Timestamp: 1780690870 | Timestamp [UTC]: 2026-06-05 20:21:10 | Age [y:d:h:m:s]: 00:003:04:25:37 |
| Block: 5689 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2197 | RingCT/type: yes/0 |
| Extra: 01cfeb4328bdf3c711f0fd2ce171ccf704e62a32dee70ac0c2ef725c1b5fbbf2a3020900000001e49593ff00 | ||
1 output(s) for total of 34.804719656659 HMNY
| stealth address | amount | amount idx | tag |
| 00: 28bb75e96771136580ee436aae4e05123de2788e56547163ab0a5e5e2a1b91f7 | 34.804719656659 | 7140 of 0 | <df> |
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": 5749,
"vin": [ {
"gen": {
"height": 5689
}
}
],
"vout": [ {
"amount": 34804719656659,
"target": {
"tagged_key": {
"key": "28bb75e96771136580ee436aae4e05123de2788e56547163ab0a5e5e2a1b91f7",
"view_tag": "df"
}
}
}
],
"extra": [ 1, 207, 235, 67, 40, 189, 243, 199, 17, 240, 253, 44, 225, 113, 204, 247, 4, 230, 42, 50, 222, 231, 10, 192, 194, 239, 114, 92, 27, 95, 187, 242, 163, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}