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: 621009ea71f82bbdbb1e51fe0dc5bbad315789853e5fc8dcb101d34f779802c0
Tx prefix hash: bad818a3a744a7b25a099b24d4ee058d201963f706c652c27098e65f86069f6b
Tx public key: ed086c2c33fad8ee0b52e3b6b7675b701c740084be0a806e611a5fdd62eabd80
| Timestamp: 1779936188 | Timestamp [UTC]: 2026-05-28 02:43:08 | Age [y:d:h:m:s]: 00:011:22:52:49 |
| Block: 3441 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 4445 | RingCT/type: yes/0 |
| Extra: 01ed086c2c33fad8ee0b52e3b6b7675b701c740084be0a806e611a5fdd62eabd8002090000000226697be300 | ||
1 output(s) for total of 34.954273074782 HMNY
| stealth address | amount | amount idx | tag |
| 00: ad0194d9807578b55412b1e5abb69da9a359071dd09540741d5779782d4a984a | 34.954273074782 | 4158 of 0 | <67> |
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": 3501,
"vin": [ {
"gen": {
"height": 3441
}
}
],
"vout": [ {
"amount": 34954273074782,
"target": {
"tagged_key": {
"key": "ad0194d9807578b55412b1e5abb69da9a359071dd09540741d5779782d4a984a",
"view_tag": "67"
}
}
}
],
"extra": [ 1, 237, 8, 108, 44, 51, 250, 216, 238, 11, 82, 227, 182, 183, 103, 91, 112, 28, 116, 0, 132, 190, 10, 128, 110, 97, 26, 95, 221, 98, 234, 189, 128, 2, 9, 0, 0, 0, 2, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}