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: 1c12be01563dd5e31df25ad0df2e538a200de4df58d23be7ca63f3996af761bb
Tx prefix hash: 5f9d9d383c4a89f97d7771f3cac600565674f78f725f089e540075ea0d0cadfc
Tx public key: b6faffc40021236795a5f2010b5b890dd11daf34a6b15f6717a3a60fb15d6160
| Timestamp: 1780078444 | Timestamp [UTC]: 2026-05-29 18:14:04 | Age [y:d:h:m:s]: 00:018:14:15:08 |
| Block: 4728 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 4017 | RingCT/type: yes/0 |
| Extra: 01b6faffc40021236795a5f2010b5b890dd11daf34a6b15f6717a3a60fb15d616002090000000226697be300 | ||
1 output(s) for total of 34.868573950735 HMNY
| stealth address | amount | amount idx | tag |
| 00: bf45e27ea482753cf280ac864b7c82c19f20636b142ab23f086b28861fefcfd4 | 34.868573950735 | 5942 of 0 | <4d> |
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": 4788,
"vin": [ {
"gen": {
"height": 4728
}
}
],
"vout": [ {
"amount": 34868573950735,
"target": {
"tagged_key": {
"key": "bf45e27ea482753cf280ac864b7c82c19f20636b142ab23f086b28861fefcfd4",
"view_tag": "4d"
}
}
}
],
"extra": [ 1, 182, 250, 255, 196, 0, 33, 35, 103, 149, 165, 242, 1, 11, 91, 137, 13, 209, 29, 175, 52, 166, 177, 95, 103, 23, 163, 166, 15, 177, 93, 97, 96, 2, 9, 0, 0, 0, 2, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}