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: 44b1723fe10ee5d84b6cf729b44fdce2b84647aeef1597991e6698df2a96808f
Tx prefix hash: 17039cad93b21c7910df3f12f594b73ad364f06836094bf8f5b1db816ad8df65
Tx public key: 2ebb9639da6b479ab83594c6aeb09ede07118fd1d1635de217f538c6da5b1d15
| Timestamp: 1779847557 | Timestamp [UTC]: 2026-05-27 02:05:57 | Age [y:d:h:m:s]: 00:013:00:34:39 |
| Block: 2480 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 5416 | RingCT/type: yes/0 |
| Extra: 012ebb9639da6b479ab83594c6aeb09ede07118fd1d1635de217f538c6da5b1d1502090000000226697be300 | ||
1 output(s) for total of 35.018401746242 HMNY
| stealth address | amount | amount idx | tag |
| 00: 22abb4e29d342295b8ef41ebd77cfda82a3ae15cb7880d2aee4db8c73eeb36c1 | 35.018401746242 | 2916 of 0 | <a5> |
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": 2540,
"vin": [ {
"gen": {
"height": 2480
}
}
],
"vout": [ {
"amount": 35018401746242,
"target": {
"tagged_key": {
"key": "22abb4e29d342295b8ef41ebd77cfda82a3ae15cb7880d2aee4db8c73eeb36c1",
"view_tag": "a5"
}
}
}
],
"extra": [ 1, 46, 187, 150, 57, 218, 107, 71, 154, 184, 53, 148, 198, 174, 176, 158, 222, 7, 17, 143, 209, 209, 99, 93, 226, 23, 245, 56, 198, 218, 91, 29, 21, 2, 9, 0, 0, 0, 2, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}