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: 2485c7f20c3f2a77927957d91032a7ced3ad0d4690bb4cdd02d0866cf43834e4
Tx prefix hash: 09bc792e73b56aaeef78b80f9143b36c25dfa8754c31861a6dc9401e9e77d009
Tx public key: 60c03610c685185e418a49a98fe3140dc0b3e1ff246e2e8c345cfdc72355300b
| Timestamp: 1780010802 | Timestamp [UTC]: 2026-05-28 23:26:42 | Age [y:d:h:m:s]: 00:011:02:09:15 |
| Block: 4094 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3792 | RingCT/type: yes/0 |
| Extra: 0160c03610c685185e418a49a98fe3140dc0b3e1ff246e2e8c345cfdc72355300b02090000000126697be300 | ||
1 output(s) for total of 34.910764633587 HMNY
| stealth address | amount | amount idx | tag |
| 00: 1c2fb5b0509ec2bba39fe76ef56065baf29bb835a8f14d57f93dcfbfb7394403 | 34.910764633587 | 5095 of 0 | <8a> |
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": 4154,
"vin": [ {
"gen": {
"height": 4094
}
}
],
"vout": [ {
"amount": 34910764633587,
"target": {
"tagged_key": {
"key": "1c2fb5b0509ec2bba39fe76ef56065baf29bb835a8f14d57f93dcfbfb7394403",
"view_tag": "8a"
}
}
}
],
"extra": [ 1, 96, 192, 54, 16, 198, 133, 24, 94, 65, 138, 73, 169, 143, 227, 20, 13, 192, 179, 225, 255, 36, 110, 46, 140, 52, 92, 253, 199, 35, 85, 48, 11, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}