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: 1282653b13f8d53a167f73c8110d83e710e2d2379c18c308d2fe959e799c716a
Tx prefix hash: eadf89786ff833b546e50aaf6aab6a5e46ea2fef919a23ea488341b6aff5fea0
Tx public key: af281cded753107640e172ed30add28aa5587b8da0305481ac71b3375024aa30
| Timestamp: 1779789242 | Timestamp [UTC]: 2026-05-26 09:54:02 | Age [y:d:h:m:s]: 00:013:16:18:00 |
| Block: 2205 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 5681 | RingCT/type: yes/0 |
| Extra: 01af281cded753107640e172ed30add28aa5587b8da0305481ac71b3375024aa3002090000000226697be300 | ||
1 output(s) for total of 35.036774464470 HMNY
| stealth address | amount | amount idx | tag |
| 00: 419e3bbcaafeafd7bcec998ce2e2cafbea7f76ead0a773c5f99e4e13ccdc2e89 | 35.036774464470 | 2551 of 0 | <42> |
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": 2265,
"vin": [ {
"gen": {
"height": 2205
}
}
],
"vout": [ {
"amount": 35036774464470,
"target": {
"tagged_key": {
"key": "419e3bbcaafeafd7bcec998ce2e2cafbea7f76ead0a773c5f99e4e13ccdc2e89",
"view_tag": "42"
}
}
}
],
"extra": [ 1, 175, 40, 28, 222, 215, 83, 16, 118, 64, 225, 114, 237, 48, 173, 210, 138, 165, 88, 123, 141, 160, 48, 84, 129, 172, 113, 179, 55, 80, 36, 170, 48, 2, 9, 0, 0, 0, 2, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}