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: a70df4710ea8e4efca59a81fafce3ef4aab03ac66c347ca50969cf3d7b0948bd
Tx prefix hash: f0ee8368e87b996c147a056c482cb3edb0be963ef182ce829a13d655f01616ea
Tx public key: a56fb9d8f4385402564f562d19d7c7034d10f7f303dc6e121371b1a052406050
| Timestamp: 1780072185 | Timestamp [UTC]: 2026-05-29 16:29:45 | Age [y:d:h:m:s]: 00:014:18:32:31 |
| Block: 4654 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 4091 | RingCT/type: yes/0 |
| Extra: 01a56fb9d8f4385402564f562d19d7c7034d10f7f303dc6e121371b1a05240605002090000000326697be300 | ||
1 output(s) for total of 34.873495785751 HMNY
| stealth address | amount | amount idx | tag |
| 00: 73d0237921c95357f35691fa0e9c6edb66c4d2469088cc010e1faa564e763c77 | 34.873495785751 | 5847 of 0 | <dd> |
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": 4714,
"vin": [ {
"gen": {
"height": 4654
}
}
],
"vout": [ {
"amount": 34873495785751,
"target": {
"tagged_key": {
"key": "73d0237921c95357f35691fa0e9c6edb66c4d2469088cc010e1faa564e763c77",
"view_tag": "dd"
}
}
}
],
"extra": [ 1, 165, 111, 185, 216, 244, 56, 84, 2, 86, 79, 86, 45, 25, 215, 199, 3, 77, 16, 247, 243, 3, 220, 110, 18, 19, 113, 177, 160, 82, 64, 96, 80, 2, 9, 0, 0, 0, 3, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}