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: 8d1926568979e313053f731bba9bfe73227209f25749f43c73cb9c4339b7a147
Tx prefix hash: f4950e3c592675c1176e45d86dc872e29a8cd7ed956a42848e3d88f223a4c478
Tx public key: d248c5e9f3add5bedd0bb1239d2be3e1523e8c0d90fbc04d2a18cf81a138b05a
| Timestamp: 1779966515 | Timestamp [UTC]: 2026-05-28 11:08:35 | Age [y:d:h:m:s]: 00:011:13:38:12 |
| Block: 3810 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 4076 | RingCT/type: yes/0 |
| Extra: 01d248c5e9f3add5bedd0bb1239d2be3e1523e8c0d90fbc04d2a18cf81a138b05a02090000000126697be300 | ||
1 output(s) for total of 34.929680482170 HMNY
| stealth address | amount | amount idx | tag |
| 00: cf7a2dabdabe5c28bb6b5177c7004ec8a3de358b018be6afccfc679df06b1372 | 34.929680482170 | 4639 of 0 | <7e> |
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": 3870,
"vin": [ {
"gen": {
"height": 3810
}
}
],
"vout": [ {
"amount": 34929680482170,
"target": {
"tagged_key": {
"key": "cf7a2dabdabe5c28bb6b5177c7004ec8a3de358b018be6afccfc679df06b1372",
"view_tag": "7e"
}
}
}
],
"extra": [ 1, 210, 72, 197, 233, 243, 173, 213, 190, 221, 11, 177, 35, 157, 43, 227, 225, 82, 62, 140, 13, 144, 251, 192, 77, 42, 24, 207, 129, 161, 56, 176, 90, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}